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

Application configuration management capabilities

Operating an application successfully in the Kubernetes environment requires a few capabilities from the perspective of configuration management. Here is a list of critical configuration management capabilities:

  • Packaging: As discussed several times, deploying an application into Kubernetes involves configuring multiple resources. It requires a capability where we can package all these resources into a single bundle.
  • Life cycle management: An application and all its dependencies must be executed into the cluster as a single deployment supporting the required release management constructs such as rollout, rollback, version management, and blue-green deployment.
  • Application discovery: This is a capability that is required for day-to-day operations. It will enable any discovery tools to dashboard a list of applications deployed, their version, and dependencies.
  • Application description customization: Not all environments...