fleet apply

Create bundles from directories, and output them or apply them on a cluster

  1. fleet apply [flags] BUNDLE_NAME PATH...

Options

  1. -b, --bundle-file string Location of the raw Bundle resource yaml
  2. --cacerts-file string Path of custom cacerts for helm repo
  3. --commit string Commit to assign to the bundle
  4. -c, --compress Force all resources to be compress
  5. --context string kubeconfig context for authentication
  6. --correct-drift Rollback any change made from outside of Fleet
  7. --correct-drift-force Use --force when correcting drift. Resources can be deleted and recreated
  8. --correct-drift-keep-fail-history Keep helm history for failed rollbacks
  9. --debug Turn on debug logging
  10. --debug-level int If debugging is enabled, set klog -v=X
  11. --delete-namespace Delete GitRepo target namespace after the GitRepo or Bundle is deleted
  12. -f, --file string Location of the fleet.yaml
  13. --helm-credentials-by-path-file string Path of file containing helm credentials for paths
  14. --helm-repo-url-regex string Helm credentials will be used if the helm repo matches this regex. Credentials will always be used if this is empty or not provided
  15. -h, --help help for apply
  16. --keep-resources Keep resources created after the GitRepo or Bundle is deleted
  17. -k, --kubeconfig string kubeconfig for authentication
  18. -l, --label strings Labels to apply to created bundles
  19. -n, --namespace string namespace (default "fleet-local")
  20. --oci-basic-http Use HTTP to access the OCI regustry
  21. --oci-insecure Allow connections to OCI registry without certs
  22. --oci-password-file string Path of file containing basic auth password for OCI registry
  23. --oci-reference string OCI registry reference
  24. --ociusername string Basic auth username for OCI registry
  25. -o, --output string Output contents to file or - for stdout
  26. --password-file string Path of file containing basic auth password for helm repo
  27. --paused Create bundles in a paused state
  28. -a, --service-account string Service account to assign to bundle created
  29. --ssh-privatekey-file string Path of ssh-private-key for helm repo
  30. --sync-generation int Generation number used to force sync the deployment
  31. --target-namespace string Ensure this bundle goes to this target namespace
  32. --targets-file string Addition source of targets and restrictions to be append
  33. --username string Basic auth username for helm repo
  34. --driven-scan Use driven scan. Bundles are defined by the user.
  35. Paths will be defined by the tuple <base, options> separated by a separator.
  36. The default separator is the character ':'. If you need to use a different one,
  37. use the --driven-scan-sep flag.
  38. --driven-scan-sep Separator used for user-driven bundle generation paths. (default: ':')

Good to know

fleet apply now reads known_hosts data from an environment variable (FLEET_KNOWN_HOSTS), similarly to what the git cloner does.

This means that, should you want to run fleet apply directly on your host machine, providing it a custom value of KNOWN_HOSTS, you will need to export FLEET_KNOWN_HOSTS beforehand or run it as FLEET_KNOWN_HOSTS=<your_entries> fleet apply <args>.

SEE ALSO