Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
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

Open Application Model

OAM is an open source standard developed by Microsoft and Alibaba to guide us in creating higher-level abstraction APIs for application deployment. In other words, it’s about creating a model for application configuration management using composition as a pattern. The standard focus on addressing the following three problems:

  • Developer focus: Exposing developers directly to Kubernetes configuration management to deploy the applications will make them spend time figuring out infrastructure details rather than application focus. Hence, OAM attempts to keep developers focused on the application.
  • Vendor dependency: Configuring applications usually tends to depend on the underlying infrastructure. Completely decoupling the application configuration from the underlying infrastructure can enable the portability of workloads. Kubernetes does this to an extent, but the area requires more work with cross-cutting concerns and COTS dependencies.
  • Extendibility...
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