Chapter 5. The Future of Cluster API and Kubernetes
Cloud native architecture is not going away. To drive scale, the enterprise relies on modular, mircroservice-based applications. Automation and orchestration of complex deployments will only become more critical as time goes on. Containers and Kubernetes adoption will continue to accelerate, with more and more companies deploying multiple clusters that employ different Kubernetes distributions across a variety of environments.
As use cases become more sophisticated and diverse, bare metal and edge deployments will become more important. The ecosystem must grow to meet these challenges, along with providers and tooling for new environments. Kubernetes itself is approaching maturity but will remain the nexus of an ecosystem of innovation, with continual development of integrations and supporting tools.
Experimental Features
Cluster API includes experimental features that provide a glimpse into what the future might hold. These features live in the exp directory and can be enabled by users who want to experiment.
At the time of this writing, Cluster API provides the following experimental features:
ClusterClass-
An easier, more flexible way to create clusters
ClusterResourceSet-
A way to apply a set of resources to a group of clusters
- Ignition bootstrap configuration
-
A bootstrapping engine for bringing up workload nodes that use Ignition-based Linux operating systems
MachinePool-
A feature similar to
MachineDeployment ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access