Dedicated instances – instance per cluster with Flux CD

In the realm of GitOps tools, the distinction between Argo CD and Flux CD is crucial, particularly when considering their application in dedicated instances per cluster. While Argo CD is a well-known entity in the GitOps conversation, Flux CD holds a significant place, with a robust community and a substantial user base. This diversity of tools is essential to understanding the range of options available for Kubernetes cluster management.

My journey in GitOps began with Flux CD, a tool that served effectively over a long period, especially in projects where scaling and managing multiple clusters wasn’t a requirement. This context-specific suitability of Flux CD stems from its distinct approach and capabilities compared to Argo CD.

At first glance, the use of Flux CD might appear like that of Argo CD, almost as if it’s a simple icon swap, as visually represented in Figure 6.3, where there’s a dedicated...