Kubernetes 1.25 has been officially released.
1.25 A total of 40 functional changes are included, including:
- 15 enhancements are entering alpha phase
- 10 enhancements are being upgraded to beta
- 13 enhancements are being upgraded to stable stage
- Two features have been marked as deprecated or deleted
Major changes
Cgroup v2 supports official GA
Cgroups is one of the key Linux kernel functions for organizing and managing container resources on nodes. In the early days of Kubernetes, all container runtimes were built using cgroup v1. Now, cgroup v2 support has been upgraded to GA status. With cgroups v2, container workloads will work more securely, including rootless containers, and use the latest kernel features more reliably.
Time zone support in CronJob is upgraded to beta
CronJob instances are created from the plan provided in the resource specification. However, the time zone of the newly created resource depends on where the Controller Manager runs. With the new enhancements, you will get a new field, spec.timeZone, in which you can use the valid time zone in the tz database.
Delete PodSecurityPolicy
In Kubernetes 1.25, PodSecurityPolicy was completely removed after the 1.21 version was abandoned. PodSecurityPolicy is a solution to define the rules of Pod functions, but it has become complex and confusing over time. On the contrary, Kubernetes has now implemented a Pod security admission controller with a clear migration path.
Retroactive default StorageClass assignment (alpha version)
The default storage class is mainly configured by the cluster administrator during cluster creation. However, when the underlying storage provider or business requirements change, you should also change the default storage class in the cluster. The new alpha function focuses on changing the Kubernetes behavior to have traceability to PVC without any storage classes.
Automatically refresh the official CVE source (alpha version)
Kubernetes is one of the most active open source repositories, so there are many CVE related problems and PRs that cannot be filtered. The new alpha function ensures that problems and PRs are flagged with the help of automation. This new method will allow you to list CVEs with relevant information as end users, maintainers or platform providers.
The default is seccomp (upgrade to beta)
Kubernetes allows to improve container security by defining seccomp configuration files; Since version 1.22, it has been an alpha function. By default, enabling Seccomp will add a security layer to prevent CVE and 0-days. Now this feature has been upgraded to beta in version 1.25.
The theme of Kubernetes version 1.25 is 「Combiner」 The team hopes to express the spirit of respect, collaboration and openness through this version, which will transform everyone from independent developers, writers and users scattered around the world into a joint force that can change the world.
Release Announcement | Changelog
