You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I really would like to see two important facts in this page. And in the quickstart guide, but I'll open another issue for that.
if no kustomization.yaml (Kubernetes, not the Flux2 one) is present, all manifests from all subdirectories are used.
you can exclude manifests by using a kustomization.yaml that does not contain the manifests you want to exclude.
Something like this:
By default, Flux uses all manifests in the path specified by the Kustomization, if no kustomization.yaml is present. In this case a kustomization.yaml will be generated on the fly using all the manifests found in this directory and its subdirectories.
If a kustomization.yaml is found, only those manifests mentioned in it will be used. This is useful to exclude manifests or folders from being used, to e.g. use them in a separate kustomization due to ordering issues
The text was updated successfully, but these errors were encountered:
https://fluxcd.io/flux/components/kustomize/kustomizations/#generating-a-kustomizationyaml-file
(I wanted to open a PR for this page, but did not find it in https://github.com/fluxcd/website).
I really would like to see two important facts in this page. And in the quickstart guide, but I'll open another issue for that.
Something like this:
The text was updated successfully, but these errors were encountered: