Understanding the Flux operational model

Flux must be installed on a Kubernetes cluster to take advantage of its workload management capabilities with GitOps. The installation process, known as the bootstrapping process, deploys Flux components into a cluster and configures a Git repository to manage Flux resources. We'll refer to this as the Flux management repository to distinguish it from other repositories that may be used to store the desired state.

Flux manages itself using GitOps. It drives all of its operations on the cluster from Kubernetes manifests stored within the Flux management repository created during the bootstrapping process. When a new Flux resource, like a source, is created, its declarative configuration must be committed within the Flux management repository, which is separate from the Git repository that stores a system's desired state. After bootstrapping Flux, it syncs with the Flux management repository and monitors it for new Flux resources, applying them to the cluster when detected.

Get hands-on with 1200+ tech skills courses.