Skip to content

Commit 9ae23e1

Browse files
author
Johannes Kastl
committed
content/en/flux/guides/repository-structure.md: add preface regarding the presence of a kustomization.yaml and the consequences, i.e. that files can be excluded/ignored by using a kustomization.yaml
1 parent 33e3c70 commit 9ae23e1

File tree

1 file changed

+15
-0
lines changed

1 file changed

+15
-0
lines changed

content/en/flux/guides/repository-structure.md

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,21 @@ weight: 10
88
This guide walks you through several approaches of organizing repositories
99
for a smooth GitOps experience with Flux.
1010

11+
## Preface
12+
13+
Flux by default uses all manifests in a directory and its subdirectories, unless
14+
it finds a `kustomization.yaml` file containing a Kubernetes kustomization
15+
(`kustomize.config.k8s.io/v1beta1`, not the Flux2 kind).
16+
17+
If there is no `kustomization.yaml`, one will be generated on-the-fly, using all
18+
manifests found in the directory and its subdirectories.
19+
20+
If there is a `kustomization.yaml` file, it is used directly. In this case, only
21+
the manifests mentioned in the file are being used.
22+
23+
This is a nice way to exclude files from being used, in case those files are to
24+
be used by a second Flux Kustomization.
25+
1126
## Monorepo
1227

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

0 commit comments

Comments
 (0)