Kubernetes is becoming the dominant app platform for delivering a range of applications but it also leads to increasing 'sprawl' of Kubernetes clusters, with large businesses using it everywhere. To manage this, Kubernetes can become a natural control point for managing other clusters of it. Using Kubernetes as a control plane can manage the 'thin layer' of Kubernetes, providing a single control point for managing Kubernetes clusters across different providers and achieve the Holy Grail of “hybrid multicloud."
Increasing sprawl of Kubernetes clusters is a growing concern as organizations struggle to manage Kubernetes at scale.
Kubernetes is emerging as the default standard for delivering a range of applications from cloud-native to legacy monolithic applications and virtualization.
In large organisations, Kubernetes clusters can sprawl across multiple providers and location, making it difficult to manage.
Using Kubernetes as a control point can manage the 'thin layer' of Kubernetes, providing a single control point for managing Kubernetes clusters across different providers and achieve the Holy Grail of “hybrid multicloud."
Cluster API (CAPI) and its providers allow Kubernetes to manage Kubernetes due to its control point capability.
Kubernetes has a baked-in architecture that assists with operations, allowing proper tiering of payloads (pods), extensible API, and more.
Kubernetes was not the first attempt at an application platform; WebLogic, WebSphere and virtualization came before it.
As a control point, Kubernetes can manage other control points and legacy control points were far less likely to have an API-enabled control point.
Kubernetes is considered the 80-90% solution that effectively solves application packaging, deployment, and operations problems due to its extensible architecture and friendly API.