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 OAM personas

We’ve touched upon OAM specifications several times throughout this book. We will refresh the same topic from the perspective of organizational structure. We will take some inspiration from the OAM model to organize the platform and its ecosystem. OAM proposes the following three personas to deploy and manage cloud-native applications:

  • Application developer: Concentrates on application development, keeping the entire emphasis on developing features that add value to customers directly.
  • Application operator: Offloads the complexity of configuring the applications in the cloud-native ecosystem from application developers. Enables the application development team to move faster with feature development. Application operators contribute to the end consumer indirectly.
  • Infrastructure operator: Offloads the complexity of configuring the cloud, other infrastructure, and services across the organization. It allows the application operator to focus on...