Member-only story
How to Continuously Deliver Kubernetes Applications With Flux CD
GitOps for your Kubernetes workloads
Flux CD is a continuous delivery tool that is quickly gaining popularity. Weaveworks initially developed the project, and they open-sourced it to the Cloud Native Computing Foundation.
The reasons for its success are that it is Kubernetes-aware and straightforward to set up. The most promising feature it delivers is that it allows teams to manage their Kubernetes deployments declaratively.
Flux CD synchronises the Kubernetes manifests stored in the source code repository with the Kubernetes cluster through periodically polling the repository, so teams don’t need to worry about running kubectl commands and monitoring the environment to see if they have deployed the right workloads. Instead, Flux CD ensures that the Kubernetes cluster is always in sync with the configuration defined in the source code repository.
It allows teams to achieve GitOps, which has the following principles:
- Git is the single source of truth.
- Git is the single place to operate all environments, and all configurations are code.
- All changes are observable/verifiable.
