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

Multi-tenant control plane patterns

Typically, multiple product teams will have to access the control plane platform to take advantage of the composition recipes built by the platform engineers. The section covers different patterns that Crossplane supports to enable a multi-tenant control plane. The following are the key two patterns Crossplane users can choose from:

  • Multi-tenancy with a single cluster
  • Multi-tenancy with multiple clusters

Multi-tenancy with a single cluster

Multi-tenancy with a single cluster is a pattern where all the product teams use a single Crossplane control plane. The control plane is configured to enable multi-tenancy in the same cluster itself. The following facts describe what this setup will look like:

  • The product teams are isolated with the namespace Kubernetes construct. Each product team should be assigned a namespace.
  • As mentioned previously in an earlier discussion about the difference between XR and Claim, Claims...