WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
Skip to content

Kustomization - Generating a kustomization.yaml file #1667

@johanneskastl

Description

@johanneskastl

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.

  • 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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions