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

Unified automation scope

Most of us will have different perceptions of what we mean by unified application and infrastructure automation. This section will help us understand the scope with a bit more clarity. Any application/product that we deploy is mostly a combination of custom-developed bespoke applications and common off-the-shelf (COTS) components. The term bespoke application means custom-written software for our requirements with a specific purpose. Bespoke applications are generally stateless, containerized workloads. From the perspective of Kubernetes, they are workloads that run on Pods, the basic unit of computing in Kubernetes. COTS components are generally stateful infrastructure components, such as databases, cache systems, storage systems, and messaging systems. In the cloud-native era, most COTS components are black-box, fully managed software as a service (SaaS) or platform as a service (PaaS). COTS vendors expose CRUD APIs to work with the resource with precise...