Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
End-to-End Automation with Kubernetes and Crossplane

You're reading from   End-to-End Automation with Kubernetes and Crossplane Develop a control plane-based platform for unified infrastructure, services, and application automation

Arrow left icon
Product type Paperback
Published in Aug 2022
Publisher Packt
ISBN-13 9781801811545
Length 250 pages
Edition 1st Edition
Concepts
Arrow right icon
Author (1):
Arrow left icon
Arun Ramakani Arun Ramakani
Author Profile Icon Arun Ramakani
Arun Ramakani
Arrow right icon
View More author details
Toc

Table of Contents (16) Chapters Close

Preface 1. Part 1: The Kubernetes Disruption
2. Chapter 1: Introducing the New Operating Model FREE CHAPTER 3. Chapter 2: Examining the State of Infrastructure Automation 4. Part 2: Building a Modern Infrastructure Platform
5. Chapter 3: Automating Infrastructure with Crossplane 6. Chapter 4: Composing Infrastructure with Crossplane 7. Chapter 5: Exploring Infrastructure Platform Patterns 8. Chapter 6: More Crossplane Patterns 9. Chapter 7: Extending and Scaling Crossplane 10. Part 3:Configuration Management Tools and Recipes
11. Chapter 8: Knowing the Trade-offs 12. Chapter 9: Using Helm, Kustomize, and KubeVela 13. Chapter 10: Onboarding Applications with Crossplane 14. Chapter 11: Driving the Platform Adoption 15. Other Books You May Enjoy

Automating the application deployment environment

The complete Kubernetes cluster creation and configuring of the cross-cutting concerns will be automated using this step. We will develop an XR/claim API, which does the following:

  1. Provisions a remote GKE cluster
  2. Sets up Helm and the Kubernetes provider configuration for the GKE cluster
  3. Installs Argo CD using the Helm provider into the product-a GKE cluster

Let’s look at the XRD and composition to understand the API in detail (refer to the XRD and composition in the book’s GitHub repository). We will capture two mandatory parameters (node count and machine size). The size parameter takes either BIG or SMALL as an enum value. Inside the composition, we have composed five resources. The following is the list of resources and their purpose:

  • Cluster and NodePool: Cluster and NodePool are two relevant resources responsible for GKE cluster provisioning. It is very similar to the way we provisioned...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at £16.99/month. Cancel anytime