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

Product type Paperback

Published in Aug 2022

Publisher Packt

ISBN-13 9781801811545

Length 250 pages

Edition 1st Edition

Tools

Crossplane

Concepts

DevOps

Author (1):

Arun Ramakani

View More author details

Table of Contents (16) Chapters

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

The Kubernetes journey

The Kubernetes journey to become the leading container orchestration platform has seen many fascinating moments. Kubernetes was an open source initiative by a few Google engineers based on an internal project called Borg. From day one, Kubernetes had the advantage of heavy production usage at Google and more than a decade of active development as Borg. Soon, it became more than a small set of Google engineers, with overwhelming community support. The container orchestration war was a tough fight between Docker, Mesosphere DC/OS, Kubernetes, Cloud Foundry, and AWS Elastic Container Service (ECS) from 2015. Kubernetes was outperforming its peers slowly and steadily.

Initially, Docker, Mesosphere, and Cloud Foundry announced native support for Kubernetes. Finally, in 2017, AWS announced ECS for Kubernetes. Eventually, all the cloud providers came up with a managed Kubernetes offering. The rivals had no choice other than to provide native support for Kubernetes because of its efficacy and adoption. These were the winning moments for Kubernetes in the container orchestration war. Furthermore, it continued to grow to become the core of the cloud-native ecosystem, with many tools and patterns evolving around it. The following diagram illustrates the container orchestration war: