Within its 6 years of existence, Kubernetes has been the centerpiece of the Cloud Native landscape, elevating a pluggable system that contributed to the diversification of the entire ecosystem. As a result, multiple areas have been developed in the industry, galvanizing solutions for components such as network, runtime, storage, as well as cluster provisioning. One of the pivotal tools in the management of cross-public cloud infrastructure has been Cluster API, leading a unique and radical stance for Kubernetes distribution. In association with a model such as GitOps, Cluster API assembles a mechanism that leverages the concept of a cluster as a resource.

This blog post aims to outline how ClusterOps can be modeled with Cluster API manifests and automated using GitOps tools such as ArgoCD and Flux.

The Theoretical

When it comes to cluster creation, numerous solutions and distributions have been put into place to simplify the Kubernetes bootstrapping process across cloud providers. However, one of the tools that stand out in the open-source landscape is Cluster API, as it facilitates a common interface for platform creation across existing vendors (e.g. GCP, AWS, Azure, Alibaba Cloud, Packet).

Note: For a full introduction of Cluster API, refer to this blog post .

#gitops #cloud-native #argo-cd #aws #kubernetes #cloud