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

Complexity clock, requirements, and patterns

The configuration complexity clock is a concept that explains how configuration management can become complex over time. It explores different stages in the evolution of configuration management, its use cases, and its pitfalls. It was initially discussed from the perspective of application configuration in the blog post found here: http://mikehadlow.blogspot.com/2012/05/configuration-complexity-clock.html. We will look at the same concept from the Kubernetes configuration management perspective.

The configuration complexity clock

Let’s say we are deploying our first application workload into Kubernetes. To start with, every Kubernetes artifact, such as Deployment, Service, and Ingress, can be managed as individual configuration artifacts. It may not be an issue when we operate on a tiny scale. But soon we will realize that there is an issue with consistently performing releases and rollbacks as the application configuration...