Book Image

End-to-End Automation with Kubernetes and Crossplane

By : Arun Ramakani
Book Image

End-to-End Automation with Kubernetes and Crossplane

By: Arun Ramakani

Overview of this book

In the last few years, countless organizations have taken advantage of the disruptive application deployment operating model provided by Kubernetes. With Crossplane, the same benefits are coming to the world of infrastructure provisioning and management. The limitations of Infrastructure as Code with respect to drift management, role-based access control, team collaboration, and weak contract make people move towards a control-plane-based infrastructure automation, but setting it up requires a lot of know-how and effort. This book will cover a detailed journey to building a control-plane-based infrastructure automation platform with Kubernetes and Crossplane. The cloud-native landscape has an overwhelming list of configuration management tools that can make it difficult to analyze and choose. This book will guide cloud-native practitioners to select the right tools for Kubernetes configuration management that best suit the use case. You'll learn about configuration management with hands-on modules built on popular configuration management tools such as Helm, Kustomize, Argo, and KubeVela. The hands-on examples will be patterns that one can directly use in their work. By the end of this book, you'll be well-versed with building a modern infrastructure automation platform to unify application and infrastructure automation.
Table of Contents (16 chapters)
1
Part 1: The Kubernetes Disruption
4
Part 2: Building a Modern Infrastructure Platform
10
Part 3:Configuration Management Tools and Recipes

Using Helm for application deployment

Helm is one of the popular configuration management tools in the Kubernetes ecosystem. It came into existence as early as 2015. It has come a long way in evolving itself and solving all the bottlenecks. Being a Cloud Native Computing Foundation (CNCF)-graduated project shows its maturity, production readiness, and value. Here are three key concepts of Helm:

  • Charts: Charts are the basic units of applications in Helm. A chart is nothing but the bundled package of an application with all its dependencies.
  • Repository: A bundled chart requires a consistent way of storage to distribute reliably, and repositories support this requirement. While open source applications can use a public repository, private repositories can be used for proprietary applications. Starting from Helm v3.8.0, any Open Container Initiative (OCI)-compliant repository will support Helm. This means that most container registries support Helm packages as well.
  • Release...