Skip to content

Best practice for using Fleet with a GitOps workflow

License

Notifications You must be signed in to change notification settings

cdreppar/fleet-gitops

This branch is 12 commits behind fleetdm/fleet-gitops:main.

Folders and files

NameName
Last commit message
Last commit date
Aug 13, 2024
Apr 22, 2024
Aug 5, 2024
Feb 14, 2024
Apr 12, 2024
Jul 18, 2024
Aug 5, 2024
May 29, 2024

Repository files navigation

Fleet GitOps

This is the starter repository for using Fleet with a GitOps workflow.

How to set up your GitOps workflow:

  1. Clone this repository.

  2. If you do not have a Premium Fleet license, delete the teams folder.

  3. Make any changes to policies, queries, controls, and more defined in the files.

  4. Create your own GitHub repository.

  5. Add FLEET_URL and FLEET_API_TOKEN secrets to your new repository's secrets. Learn how here. Set FLEET_URL to your Fleet instance's URL (ex. https://organization.fleet.com). Set FLEET_API_TOKEN to an API token for an API-only user in Fleet. Learn how here.

  6. Push your cloned and modified code to your repo.

  7. In GitHub, enable the Apply latest configuration to Fleet GitHub Actions workflow, and run workflow manually. Now, when anyone pushes a new commit, the action will run and update Fleet.

For all configuration options, go to GitOps reference in the Fleet documentation.

About

Best practice for using Fleet with a GitOps workflow

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • Shell 100.0%