The presentation discusses the intertwinement between different tools in the cloud native ecosystem, specifically focusing on the use of Cluster API and GitHub's in infrastructure provisioning.
- Cluster API and Tinkerbell can be used to deploy Kubernetes on bare metal.
- GitHub's can be used to define the desired state of the infrastructure and introduce automation.
- Argo CD and Helm can be used to manage and apply changes to the infrastructure.
- Introducing templating and automation can simplify the management of multiple clusters.
The speaker demonstrates a live demo of using Cluster API, GitHub's, Argo CD, and Helm to manage and apply changes to a target cluster.
Within its 8 years of existence, Kubernetes has been the gravitational center of the Cloud Native, elevating a pluggable system that diversified the entire ecosystem. Multiple areas emerged in the industry, galvanizing solutions for components such as network, runtime, storage, and cluster provisioning. The maturity of the cloud native landscape is led by the wider adoption of enterprise and large organizations. However, for these companies deployment and handling of bare-metal infrastructure has always been essential. A pivotal tool to manage cross-provider 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 talk will outline how cloud native tools, such as Tinkerbell and Cluster API unlock a robust deployment of bare-metal infrastructure. Attendees will acquire an understanding of why the usage of ClusterAPI and provisioning automation with GitOps tools, such as ArgoCD, is a powerful concept that leads an organization towards the discovery of a modernized provisioning model.