As Kubernetes adoption grows, maintaining consistency across clusters becomes increasingly challenging, especially during upgrades. Kubernetes upgrades can be complex due to several factors, such as managing dependencies on specific add-on versions and handling deprecated and removed API versions.

This session addresses repository standardization within a GitOps framework. Join us to explore best practices for organizing repositories to improve upgrade management and consistency across Kubernetes environments. We’ll examine different approaches, from MonoRepo strategies (for all components or just add-ons) to a repo-per-cluster setup, comparing the pros and cons of each. Using Fluxv2, Kustomize, OpenTofu, and Helm, we’ll provide real-world examples that illustrate how centralized repository organization enhances Kubernetes GitOps, helping attendees streamline application and add-on deployments, manage variables across clusters, and maintain consistent versions.