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

Customizing configurations with Kustomize

Be it a configuration managed by Helm or other configuration management tools, Kustomize is one of the best tools for configuration customization. Let’s look at some of the use cases for Kustomize, as follows:

  • Keeping environment-specific customization separate from the base configuration is one use case. For example, replication counts can be done in staging, while the production environment could be enabled with auto-scaling.
  • Managing cross-cutting configurations outside the base configuration is another use case. For example, the application operator working with governance-specific labels in all deployments can keep the configuration separate from the base configuration. It can enable separation of concerns (SoC) for multi-persona collaboration without friction. Injecting a service mesh configuration as a cross-cutting concern is another example.
  • The third use case is fixing vulnerabilities as a step in the configuration...