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

Framework to build a provider

To bring down the cognitive load required to develop a new provider, the Crossplane community has identified a couple of comparatively painless ways, as follows:

  • Native provider development: We have a template provider available at https://github.com/crossplane/provider-template. We can use this repository as a basic template for creating a new provider. The template has ProviderConfig, which can read credentials from the Kubernetes Secrets to manage external provider authentication and authorization. It also has a sample MR along with a controller. We can add all our new MRs and respective controllers with appropriate control theory implementation, using the CRUD APIs of the external resources. The video at https://www.youtube.com/watch?v=dhuqH308Tc0 walks us through the provider development using provider template with a hands-on example.
  • Generate provider from Terraform providers: Generating a native provider might be time-consuming. The...