Our Never-Ending Journey of GitOps Transformation with Flux CD

K8s as we know provides a declarative interface for the infrastructure & state we desire. Traditionally, in order to have efficient recoveries during catastrophic events, we save the YAML files in a folder, link to a script file and forget about it. As our project grows, files gets more complex and out of sync. Our confidence on the YAML files reflecting the current state of the cluster deteriorates too. Hence, the GitOps methodology. By using nearly the same declarations that we are already familiar & apply on our cluster anyways, we place Git as the source of truth for our cluster state. Any changes to the cluster must go through Git. This enables clear accountability & traceability, while enabling contributions from those that don’t have direct access to the cluster.

This session looks into how our company got on the GitOps bandwagon throughout the years, together with the pitfalls we faced, lessons learned and future plans. Production workload was definitely affected, but was worth it in the long run.