Commit graph

9 commits

Author SHA1 Message Date
Zachary Wasserman
5e9fe9d5a1
Transition osquery options interfaces for compatibility with fleetctl (#1649)
- Refinements to options yaml definition
- Datastore and service implementations
- Migration to bring existing options into new table format
2017-12-13 18:14:54 -05:00
Matt Mencel
80767bcf8e Update fleet-deployment.yaml (#1652)
The helm deployment of the redis service creates a service called `fleet-cache-redis`.
2017-11-28 11:05:27 -05:00
Mike Arpaia
3259e7149b
Documenting deploying Fleet on Kubernetes (#1626) 2017-11-17 12:48:59 -07:00
Zachary Wasserman
f909f4808b
Make OsqueryOptions hierarchical by platform (#1625)
- Allow overriding base config on a per-platform basis.
- Merge FIM configs into the OsqueryOptions object.
2017-11-16 10:58:47 -08:00
Mike Arpaia
b251366c1e
Each file resource should map to a Fleet data model object (#1627) 2017-11-15 21:23:37 -07:00
Mike Arpaia
607b9141ea
Remove OsqueryQueries file type (#1622) 2017-11-15 16:10:11 -07:00
Mike Arpaia
a0909e6bee
Making the file format more operator friendly (#1605) 2017-11-13 18:11:08 -07:00
Mike Arpaia
1a3bda57ab
CLI documentation and design (#1603) 2017-11-13 16:00:40 -07:00
Mike Arpaia
796e0af8be
Initial CLI and file format for fleetctl
This PR implements a program called `fleetctl` which scaffolds a high level CLI interface which can be used to manage a Fleet server. Configuration is articulated using an intent-based API that resembles the API that is used to configure Kubernetes clusters. The idea here is to use the Kubernetes file format as a pattern to reduce the need for operators to become too intimately familiar with dramatically different file formats. (#1578)
2017-11-12 11:58:19 -07:00