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

XRM detailed

Being an extension of the KRM, XRM inherits most of the standards. As discussed in Chapters 3 and 4, Crossplane inherits many standards from the Kubernetes CRDs. The opinionated XRM standards over the basic Kubernetes standards define a uniform bridge between Kubernetes and the external resource. The XRM standards cover the following characteristics:

  • Configuration fidelity
  • Spec and status configuration
  • Naming the custom and external resources
  • Configuration ownership
  • Sensitive input and output fields

We can dive into the details of each of these characteristics in the following sections.

Configuration fidelity

The MR should have all possible fields available for configuration in the external resource API. It delivers every configuration combination at the control plane level. We should leave the abstractions to encode policy and the recipe creation for the platform developers via XR. Every field available for configuration in the external...