Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

guides/repository-structure.md: add information on kustomization.yaml and ignoring/excluding files #1668

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

guides/repository-structure.md: add information on kustomization.yaml and ignoring/excluding files #1668

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions content/en/flux/guides/repository-structure.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,21 @@ weight: 10
This guide walks you through several approaches of organizing repositories
for a smooth GitOps experience with Flux.

## Preface

Flux by default uses all manifests in a directory and its subdirectories, unless
it finds a `kustomization.yaml` file containing a Kubernetes kustomization
(`kustomize.config.k8s.io/v1beta1`, not the Flux2 kind).

If there is no `kustomization.yaml`, one will be generated on-the-fly, using all
manifests found in the directory and its subdirectories.

If there is a `kustomization.yaml` file, it is used directly. In this case, only
the manifests mentioned in the file are being used.

This is a nice way to exclude files from being used, in case those files are to
be used by a second Flux Kustomization.

## Monorepo

In a monorepo approach you would store all your Kubernetes manifests in a single Git repository.
Expand Down