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

Open Application Model

OAM is an open source standard developed by Microsoft and Alibaba to guide us in creating higher-level abstraction APIs for application deployment. In other words, it’s about creating a model for application configuration management using composition as a pattern. The standard focus on addressing the following three problems:

  • Developer focus: Exposing developers directly to Kubernetes configuration management to deploy the applications will make them spend time figuring out infrastructure details rather than application focus. Hence, OAM attempts to keep developers focused on the application.
  • Vendor dependency: Configuring applications usually tends to depend on the underlying infrastructure. Completely decoupling the application configuration from the underlying infrastructure can enable the portability of workloads. Kubernetes does this to an extent, but the area requires more work with cross-cutting concerns and COTS dependencies.
  • Extendibility...