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

Building an XR

It’s time to go through a hands-on journey to build an XR from scratch. We will start with writing down the infrastructure API requirement at a high level, then provide an API specification with XRD and finally provide an implementation with a composition. We will cover the API requirement in such a way as to learn most of the configuration discussed in this chapter.

The infrastructure API requirement

We will develop an API to provision a database from Google Cloud. The following are the compliance, architecture, and product team’s requirements:

  • Compliance policy: The provisioning should be done in the us-central region to comply with the data storage regulations from the government.
  • Architecture policy: We should have two tiers of the database. For small, the disk size should be 20 GB, and it should be 40 GB for big.
  • Architecture policy: The small tier’s virtual machine should be db-g1-small, and db-n1-standard-1 for the big...
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 €18.99/month. Cancel anytime