TL;DR
Cluster API v1.12 introduces in-place updates and chained upgrades to enhance Kubernetes cluster management. In-place updates modify existing machines without deletion, while chained upgrades streamline multi-version upgrades. The release also includes improvements to immutable rollouts and various bug fixes.
Key Points
Highlight key points with color coding based on sentiment (positive, neutral, negative).Cluster API v1.12 introduces in-place updates, allowing changes to existing machines without deletion.
The new chained upgrade feature allows users to upgrade by more than one Kubernetes minor version in a single operation.
The release emphasizes simplicity and usability. It enables users to modify cluster or machine specifications to trigger updates automatically.
Enhancements include support for in-place propagation of changes affecting only Kubernetes resources which reduces unnecessary rollouts.
Cluster API v1.12 maintains its extensible nature, allowing users to create custom update extensions and influence upgrade plans.
Cluster API v1.12 introduces several technical improvements to Kubernetes cluster lifecycle management. A notable feature is the support for in-place updates, allowing modifications to existing machines without the need for deletion and recreation. This capability is now available in KubeadmControlPlane and MachineDeployments and it allows Cluster API to determine whether to perform an in-place update or a traditional rollout based on the specific changes made to cluster or machine specifications.
The release also includes a chained upgrades feature, which facilitates upgrading across multiple Kubernetes minor versions in a single operation. Users can specify a target Kubernetes version, and Cluster API manages the necessary intermediate steps. This feature is particularly useful for those looking to skip several versions during upgrades.
Additionally, Cluster API v1.12 improves immutable rollouts by allowing changes that affect only Kubernetes resources to be propagated in-place. This reduces unnecessary rollouts and optimizes pod rescheduling. The release also introduces support for the delete-first rollout strategy, beneficial in resource-constrained environments.
Key Numbers
Present key numerics and statistics in a minimalist format.The version number of the newly introduced Cluster API.
The version number of the upgraded Go dependency.
The version number of the upgraded controller-runtime dependency.
The range of supported Kubernetes versions for management clusters.
The range of supported Kubernetes versions for workload clusters.
The total number of new commits in the release.
The total number of new features added in the release.
The total number of bug fixes in the release.
Stakeholder Relationships
An interactive diagram mapping entities directly or indirectly involved in this news. Drag nodes to rearrange them and see relationship details.Organizations
Key entities and stakeholders, categorized for clarity: people, organizations, tools, events, regulatory bodies, and industries.Kubernetes SIGs are collaborative groups that focus on specific areas of Kubernetes development, including the Cluster Lifecycle SIG which is involved in Cluster API development.
Tools
Key entities and stakeholders, categorized for clarity: people, organizations, tools, events, regulatory bodies, and industries.KCP is a tool that supports in-place updates for Kubernetes clusters.
MachineDeployments is a component that supports in-place updates.
Update Extensions enable changes on existing machines.
Chained Upgrades allow clusters to upgrade by more than one minor Kubernetes version, enhancing lifecycle operations.
Feature Gates, such as the InPlaceUpdates gate, enable specific features like in-place updates in Cluster API.
Timeline of Events
Timeline of key events and milestones.Cluster API v1.12.0 was released, introducing new features for Kubernetes cluster lifecycle management.
Throughout 2025, the Cluster API community delivered several releases to enhance Kubernetes functionalities.
Cluster API v1.12 introduced in-place updates and chained upgrades to improve Kubernetes cluster lifecycle management.
A session titled "In-place Updates with Cluster API: The Sweet Spot Between Immutable and Mutable Infrastructure" is scheduled in Amsterdam.
Additional Resources
Enjoyed it?
Get weekly updates delivered straight to your inbox, it only takes 3 seconds!Subscribe to our weekly newsletter Kaptain to receive similar updates for free!
Give a Pawfive to this post!
Share with your friends and followers
Start writing about what excites you in tech — connect with developers, grow your voice, and get rewarded.
Join other developers and claim your FAUN.dev() account now!
FAUN.dev()
FAUN.dev() is a developer-first platform built with a simple goal: help engineers stay sharp without wasting their time.
Kaptain #Kubernetes
FAUN.dev()
@kaptain
