In this post, we’re excited to share that we have successfully completed the migration of our Kubernetes (K8s) add-ons as announced in our previous post. The management of these add-ons has now transitioned from our existing OpenTofu-based approach (using Terragrunt and Concourse CI) to Flux. Here is what you need to know about this migration, the benefits it brings, and what to expect moving forward.
Overview
By now you may have noticed commit messages in your repositories as follows:
These logs tell you exactly what has been changed in your cluster. The commit links to a pull request that contains the changes made to the cluster, what version of the cluster definition file was used and what release of our kubernetes stack release was used to generate the files. This increases transparency on what is configured on your cluster(s) and is a great way to track what has been changed and when. For example the following maintenance release of the kubernetes stack release:
What’s Next?
Next up is for us to prepare everything to be able to move our automation from Concourse CI to Crossplane. This will allow us to make it easier to manage and maintain our infrastructure in a more automated and controlled way. Over the summer we will be working on preparing everything to be able to make this transition.