We started this chapter with a review of the most common different kinds of configuration management strategies, and how they tend to be applied as a project grows. We discussed how the DevOps approach makes teams take ownership of their deployments and helps to fill the traditional gap between development and operations.
We saw how the latest approach called GitOps works very well with a Kubernetes cluster, as the configuration is tightly described as a set of files. We went through the advantages of using Git to track the configuration.
We introduced Flux, a tool that gets deployed inside your cluster and pulls changes from a Git repo branch. We presented an example configuration, deployed it in our local Kubernetes cluster, and configured GitHub to be able to work with it. This enabled any push to our Git branch in GitHub to be reflected in the local cluster.
We ended...