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

Understanding customers’ needs

A platform team for infrastructure means external delivery dependency. This is something that is always avoided by agile product development teams. If you have worked in a large organization, you might have noticed that the product teams are often unhappy with what the platform team offers. They have issues with the delivery timeline, backlog coupling, and weak contracts. It is critical to set up a proper interaction model between the product and platform teams to mitigate these risks. The following are qualities that a platform team should possess to match the delivery expectations of product teams in the modern software engineering era:

  • Product development practices
  • Self-service
  • Collaborative backlog management

The following section will look at the product development engineering practices for the platform team.

Product development practices

Adopting product development practices is a critical component that can...