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

The platform product life cycle and team interaction

We may start our Crossplane API development as a small proof of concept working with one of the product teams. Later, when we are comfortable with the proof of concept, we will release an alpha version asking a few teams to consume and test it. Again, when we are satisfied with the alpha version, we will ask a few more sections of the organization to adopt and go live with the API. If everything goes well, we can move the API to general availability to be consumed by anyone in the organization. It will not end there. Sometimes, we will have the requirement to deprecate the APIs and mark them for removal in the future. The following figure represents the API journey:

Figure 11.1 – Crossplane API life cycle

Every API may not go through all the phases mentioned. It may take its own path, moving from left to right and skipping some stages depending on the situation.

Information

Sometimes, we may...