Noah TalermanandRachael Shaw
62c1033868
For the following issue: - https://github.com/fleetdm/fleet/issues/41419 <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Chores** * Updated tooling and documentation wording across scripts, utilities, and infrastructure files to reflect the product terminology change from “teams” to “fleets” (references now note “fleets” and indicate the former “teams” naming). <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Rachael Shaw <r@rachael.wtf>
Kubequery and Fleet
Use the provided configuration file (kubequery-fleet.yml) to get a kubequery instance connected to Fleet.
Before deploying, first retrieve the enroll secret from Fleet by opening a web browser to the Fleet URL, going to the Hosts page, and clicking on the "Manage enroll secret" button.
Alternatively, you can get the enroll secret using fleetctl using fleetctl get enroll-secret.
Update the enroll.secret in the ConfigMap. In production, you will also need to update the tls_hostname and fleet.pem to the appropriate values. In order to download the fleet.pem certificate chain, navigate to the "Hosts> Add hosts> Advanced" tab and select "Download". Finally, deploy kubequery using kubectl
kubectl apply -f kubequery-fleet.yml
Kubernetes clusters will show up in Fleet with hostnames like kubequery <CLUSTER NAME>.
Sample reports (formerly "queries") are included in the configuration file (queries-kubequery-fleet.yml). Modify the team value in this file to reflect the appropriate fleet (formerly "team") name for your environment and apply with fleetctl.
fleetctl apply -f queries-kubequery-fleet.yml