Kubernetes Version Update
We've updated our Kubernetes platform. Version 1.30 is supported, and version 1.31 is now in preview.
By
Published on
We’ve updated our Kubernetes platform. Version 1.30 is supported, and version 1.31 is now in preview.
Updating to a newer version ensures you have access to the latest bug fixes and enhancements, which can help prevent potential issues and improve your overall experience.
We currently support Kubernetes 1.30, which means it has undergone rigorous testing and is deemed stable for production use. On the other hand, Kubernetes 1.31 is still in preview, indicating that it’s a newer release that hasn’t yet completed thorough testing and validation. While we’re excited about the new features and capabilities of version 1.31, we recommend waiting until it reaches general availability before deploying it to production environments. You can get started with Kubernetes on Leafcloud here.
Now that we’ve gotten that out of the way, let’s dive into the changes.
1.30 supported: features, changes
Version 1.30 of Kubernetes brings with it several upgrades and feature enhancements. Some key features and changes include:
-
Container Resource Based Pod Autoscaling has graduated to stable, refining the Horizontal Pod Autoscaler’s capabilities.
-
User Namespaces in Pods has moved to beta, enhancing pod security by supporting customized UID/GID ranges.
-
The introduction of Structured Parameters for Dynamic Resource Allocation, improving resource management within clusters.
-
A new ‘sleep’ action for the PreStop lifecycle hook, which is graduating to beta.
-
Node Memory Swap Support is undergoing major changes in its beta stage.
-
The kubelet now supports configuring IDs used to create user namespaces.
-
AppArmor profiles can now be configured through fields on the PodSecurityContext and container SecurityContext.
Complete 1.30 Schedule and Changelog
1.31 preview: features, changes
Key takeaways for version 1.31
-
AppArmor support for Kubernetes is graduating to stable, allowing specification of AppArmor profiles for containers or pods.
-
34 new alpha features are being introduced, including initial design for pod-level resource limits.
-
KubeProxy Ingress is being improved for better connection draining on terminating Nodes.
-
A randomized algorithm for Pod selection when downscaling ReplicaSets is being introduced.
-
The removal of all in-tree integrations with cloud providers, a major step towards making Kubernetes truly vendor-neutral.
-
The introduction of updated dynamic resource allocation (DRA) API and design, focusing on structured parameters.
Complete 1.31 Schedule and Changelog
Upcoming: 1.32
Coming up, version 1.32 of Kubernetes. We’ll be working on this next and will announce the coming update in due course.
View all Kubernetes releases here
related