Author: Mostafa Radwan

The Cloud Native Computing Foundation (CNCF) released Kubernetes 1.32, named Penelope a few weeks ago. The new release introduced support for the Graceful Shutdown of Windows Nodes, new status endpoints for core components, and asynchronous preemptions in the Kubernetes scheduler.

A key feature in Kubernetes 1.32 is the various enhancements to Dynamic Resource Allocation (DRA), a cluster-level API for requesting and sharing resources between pods and containers. These enhancements improve the ability to effectively manage resource allocation for AI/ML workloads that rely heavily on specialized hardware such as GPUs.

Some alpha features in version 1.32 include two new HTTP status endpoints /statusz and /flagz for core components such as the kube-scheduler and kube-controller-manager. This makes gathering details about a cluster’s health and configuration easier to identify and troubleshoot issues.

Another feature entering alpha in this release is asynchronous preemption in the scheduler. This mechanism allows high-priority pods to get the resources needed by evicting low-priority pods in parallel, minimizing delays in scheduling other pods in the cluster.

In addition, an enhancement to Gracefully Shut down Windows Nodes has been added to the Kublet to ensure proper lifecycle events are followed for pods. This allows pods running on Windows nodes to be gracefully terminated and workloads rescheduled without disruption. Before this enhancement, this functionality was limited only to Linux nodes.

The automatic removal of PersistantVolumeClaims(PVCs)created by StatefulSets is a stable feature in version 1.32. This streamlines storage management, especially for stateful workloads, and reduces the risk of unused resources.

This release also includes a generally available improvement to the Kubelet to generate and export OpenTelemetry trace data. This aims to make monitoring, detecting, and resolving issues related to the Kubelet easier.

Allowing anonymous authorization for configured endpoints moved to beta in this release. This enhancement is enabled by default in version 1.32 allowing cluster administrators to specify which endpoints can be accessed anonymously.

Additionally, recovery from volume expansion failure is a beta feature in the new release. This improvement allows recovery from a volume expansion failure by retrying with a smaller size, reducing the risk of data loss or corruption throughout the process.

The flowcontrol.apiserver.k8s.io/v1beta3 API related to FlowSchema and PriorityLevelConfiguration was removed in the new release. It’s part of the Kubernetes API functionality to deal with an overload of incoming requests. Users are encouraged to migrate to flowcontrol.apiserver.k8s.io/v1 which has been available since version 1.29.

According to the release notes, Kubernetes version 1.32 has 44 enhancements, including 19 entering alpha, 12 graduating to beta, and 13 becoming generally available or stable.

For more information on the Kubernetes 1.32 release, users can refer to the official release notes and documentation for a detailed overview of the enhancements and deprecations in this version or watch the upcoming CNCF webinar by the release team scheduled for Thursday, January 9th, 2025 at 5 PM UTC. The next release version 1.33 is expected in April 2025.

The Cloud Native Computing Foundation (CNCF) released Kubernetes 1.30, named Uwubernetes in April. The release introduced features such as recursive read-only mounts, job completion policy, and fast recursive SELinux label change.

One of the changes in Kubernetes 1.30 is the overhaul of memory swap support for Linux nodes. This improvement is designed to enhance system stability by providing more control over memory usage. Alongside this, the introduction of a sleep action for the PreStop lifecycle hook offers a simplified native option for managing pod termination activities and ensuring better workload management.

Alpha features in version 1.30 include the integration of the Common Expression Language (CEL) for admission control, which paves the way for more sophisticated policy controls and validation mechanisms in Kubernetes clusters. Furthermore, enhancements to service account tokens through Kubernetes Enhancement Proposals (KEP) aim to provide more secure and manageable service accounts, an essential component for maintaining secure Kubernetes environments.

Kubernetes 1.30 also brings beta support for user namespaces, a Linux feature that isolates container UIDs and GIDs from those on the host, significantly bolstering security measures.

Kat Cosgrove, from the release team, commented on Contextual Logging becoming beta in version 1.30:

This enhancement simplifies the correlation and analysis of log data across distributed systems, significantly improving the efficiency of troubleshooting efforts. By offering a clearer insight into the workings of your Kubernetes environments, Contextual Logging ensures that operational challenges are more manageable, marking a notable step forward in Kubernetes observability.

Further scheduling improvements have been made, highlighted by the introduction of MatchLabelKeys for PodAffinity and PodAntiAffinity, which allows for better pod placement strategies.

Also, the decoupling of critical components such as the TaintManager from NodeLifecycleController intends to enhance the overall maintainability of the project.

Additionally, this version presents usability upgrades to the scheduler and new structured authorization configurations, which ensure more sophisticated access controls within Kubernetes environments.

This release also deprecates several outdated features. The regression fixes for open API descriptions of imagePullSecrets and hostAliases fields are noteworthy, as consistency in these fields’ usage is crucial for operational integrity.

Additionally, this version signals the movement away from legacy security configurations in favor of more streamlined and modular approaches.

According to the release notes, Kubernetes version 1.30 has 45 enhancements, including 10 entering alpha, 18 graduating to beta, and 17 becoming generally available.

Earlier this month, the Kubernetes community celebrated 10 years since the first git commit to the project. The event known as KuberTENes was held in many places around the globe with the official one sponsored by the CNCF in Mountain View, CA, and was streamed live on its YouTube channel.

For detailed information on the Kubernetes 1.30 release, users can refer to the official release notes and documentation for a comprehensive overview of the enhancements and deprecations this version presents or watch the recording of the CNCF webinar by the release team. The next release 1.31 is expected in August 2024.