
└── production # <- path=clusters/production └── flux-systemĪfter running bootstrap you can place Kubernetes YAMLs inside a dir under pathĮ.g. ├── staging # <- path=clusters/staging │ └── flux-system # <- namespace dir generated by bootstrap │ ├── gotk-components.yaml Then itĬonfigures the target cluster to synchronize with that repository. The bootstrap git command takes an existing Git repository, clones it andĬommits the Flux components manifests to the specified branch. If your Git provider is AWS CodeCommit, Azure DevOps, Bitbucket Server, GitHub or GitLab please With support for Linux amd64, arm64 and armv7 (e.g. The Flux component images are published to DockerHub and GitHub Container Registry Idempotent, it’s safe to run the command as many times as you want. If the Flux components are present on the cluster, the bootstrapĬommand will perform an upgrade if needed. Kubernetes cluster and configure it to manage itself from a Git Using the flux bootstrap command you can install Flux on a


Configure image automation authentication.
