Kubernetes 1.31 completed the largest migration in Kubernetes history, removing the in-tree cloud provider. While the component migration is now done, this leaves some additional complexity for users and installer projects (for example, kOps or Cluster API) . We will go over those additional steps and failure points and make recommendations for cluster owners. This migration was complex and some logic had to be extracted from the core components, building four new subsystems.

Kubernetes is an open-source container orchestration platform for automating the deployment, scaling, and management of containerized applications. With Kubernetes, developers can deploy applications across clusters of machines, ensuring high availability, scalability, and resilience. Developers can learn about Kubernetes' architecture, core concepts, and deployment strategies, and gain hands-on experience with managing containerized workloads using Kubernetes.

Kubernetes

Kubernetes 1.31 has completed a significant migration by removing the in-tree cloud provider and introducing new subsystems. The migration affects the initialization process of nodes, adding complexity and potential issues during cluster bootstrapping. The Cloud Controller Manager (CCM) now handles functionalities previously managed by kube-controller-manager and kubelet. Recommendations include using host network mode, scalable resource types like Deployments or DaemonSets, targeting control plane nodes, and ensuring proper tolerations to avoid scheduling issues. Detailed guidance and an example deployment configuration are provided.

The Cloud Controller Manager Chicken and Egg Problem