actions/fluxcd-flux2
3
0
Fork 0
mirror of https://github.com/fluxcd/flux2.git synced 2026-02-25 09:01:48 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 16

Specify where to place Kubernetes manifests after bootstrap

Browse source 
Signed-off-by: Stefan Prodan <stefan.prodan@gmail.com>
This commit is contained in:
Stefan Prodan 2020-12-01 09:46:28 +02:00
parent e3d6461a80
commit bd05a8173c
No known key found for this signature in database
GPG key ID: 3299AEB0E4085BAF
1 changed files with 5 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
docs/guides/installation.md
View file

@ -84,12 +84,17 @@ cluster e.g. `clusters/staging` and `clusters/production`:
└── flux-system └── flux-system
``` ```
After running bootstrap you can place Kubernetes YAMLs inside a dir under path
e.g. `clusters/staging/my-app`, and Flux will reconcile them on your cluster.
!!! hint "Change the default branch" !!! hint "Change the default branch"
If you wish to change the branch to something else than main, create the repository manually, If you wish to change the branch to something else than main, create the repository manually,
push a branch to origin and then use `flux bootstrap <GIT-PROVIDER> --branch=your-branch`. push a branch to origin and then use `flux bootstrap <GIT-PROVIDER> --branch=your-branch`.
For examples on how you can structure your Git repository see: For examples on how you can structure your Git repository see:
* [flux2-kustomize-helm-example](https://github.com/fluxcd/flux2-kustomize-helm-example) * [flux2-kustomize-helm-example](https://github.com/fluxcd/flux2-kustomize-helm-example)
* [flux2-multi-tenancy](https://github.com/fluxcd/flux2-multi-tenancy)
### GitHub and GitHub Enterprise ### GitHub and GitHub Enterprise