Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
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

Why we need an infrastructure platform as a product

We touched on this topic a bit in Chapter 2. It is time to look back and see why we need a platform team to develop the Crossplane APIs. The following are the three key reasons:

  • Cognitive load: Any organization will tend to use a vast amount of cloud resources and other external services. These resources and services consist of tens of thousands of attributes to configure them according to the organization’s requirements. Remembering the usage of each configuration attribute involves a significant cognitive load. Suppose we attempt to build this knowledge within the product team. In that case, the team will focus on technical complexity rather than product feature development, which is of direct business interest. If you look at the CNCF cloud-native landscape, it’s vast (https://landscape.cncf.io/). Not every team can tame the terrain. It requires a specialized group to build this cognitive capability into the...
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 $19.99/month. Cancel anytime
Banner background image