Announcing the Checkpoint/Restore Working Group
… Across these scenarios, the goal is to help facilitate discussions of ideas between the Kubernetes community and the growing Checkpoint/Restore in Userspace CRIU ecosystem. …
Search
People also ask
What’s next?
If you read the Cluster API manifesto, you can see how the Cluster API subproject claims the right to remain unfinished, recognizing the need to continuously evolve, improve, and adapt to the changing needs of Cluster API’s users and the broader Cloud Native ecosystem. As Kubernetes itself continues to evolve, the Cluster API subproject will keep advancing alongside it, focusing on safer upgrades, reduced disruption, and stronger building blocks for platforms managing Kubernetes at scale. Innovation remains at the heart of Cluster API, stay tuned for an exciting 2026! Useful links: Cluster API
Cluster API v1.12: Introducing In-place Updates and Chained UpgradesKubernetes 1.35: In-Place Pod Resize Graduates to Stable
… This allows resources to be adjusted automatically and seamlessly based on usage with minimal disruption. …
Kubernetes v1.36: Declarative Validation Graduates to GA
… Beyond the core migration, declarative validation also unlocks an exciting future for the broader ecosystem. …
Cluster API v1.12: Introducing In-place Updates and Chained Upgrades
… However, while advantages of immutability are not under discussion, both Kubernetes and Cluster API are undergoing a similar journey, introducing changes that allow users to minimize workload disruption whenever possible. …
Kubernetes v1.36: Advancing Workload-Aware Scheduling
… The people working on this set of features are hoping to extend support for these fields to other disruption sources, including default preemption used in the Pod-by-Pod scheduling cycle, in future releases. apiVersion : scheduling.k8s.io/v1alpha2 kind : PodGroup metadata : name : victim-pg spec : … …
Kubernetes v1.35: Mutable PersistentVolume Node Affinity (alpha)
… While it is a simple change that removes one validation from the API server, we still have a long way to go to integrate well with the Kubernetes ecosystem. …
Kubernetes v1.35: Timbernetes (The World Tree Release)
… In the wider cloud native ecosystem, the figure goes up to 281 companies, counting 1769 total contributors. …
Kubernetes v1.32: Penelope
… In the whole Cloud Native ecosystem, the figure goes up to 433 companies counting 2441 total contributors. …
Kubernetes v1.36 Sneak Peek
… This transition reflects the same lifecycle discipline that underpins Kubernetes itself, ensuring continued evolution without abrupt disruption. …
Kubernetes v1.36: ハル (Haru)
… In the wider cloud native ecosystem, the figure goes up to 370 companies, counting 2235 total contributors. …
To show you the most relevant results, we’ve omitted some entries very similar to those already shown. Repeat the search with the omitted results included.