The Cloud Native Computing Foundation (CNCF) is out with the open source Kubernetes 1.30 release, nicknamed “Uwubernetes” by its more than a thousand contributors

The Kubernetes 1.30 update is the first update for the widely used cloud native container orchestration platform in 2024 and follows the 1.29 update that came out in December. The Kubernetes 1.30 update packs major improvements across core areas like networking, storage, scheduling and code architecture, further demonstrating Kubernetes' continued evolution to support diverse cloud native workloads and environments.

Not only is Kubernetes open source in terms of code availability, it's also a very vibrant open community of contributors. For the 1.30 release, 1,391 individuals from 863 companies contributed. Kubernetes is supported on AWS, Microsoft Azure and Google Cloud Platform as well as via numerous commercially supported enterprise distributions including Red Hat OpenShift, Canonical Kubernetes and VMware Tanzu among others.

While Kubernetes 1.30 is a serious update, the codename is a bit whimsical.

“For the people who built it, for the people who release it, and for the furries who keep all of our clusters online, we present to you Kubernetes v1.30: Uwubernetes, the cutest release to date,” The Kubernetes 1.30 release announcement states. “The name is a portmanteau of ”kubernetes“ and ”UwU,“ an emoticon used to indicate happiness or cuteness.”

Few if any developers would ever refer to networking as being 'cute' but it is a critical aspect of every Kubernetes update and the 1.30 milestone is no exception.

On the networking front, Kubernetes 1.30 brings several improvements. Among the improvements is a feature known as Topology Aware Hints. While Kubernetes is often highly distributed, sometimes it's better to keep traffic all within one zone.

“Kubernetes clusters are increasingly deployed in multizone environments,” the Kubernetes Enhancement Proposal (KEP) that details the feature states. “Network traffic is routed randomly to any endpoint matching a Service. Some users might want the traffic to stay in the same zone.”

There is also a series of updates to help improve support for dual stack IPv4/IPv6 network addressing. KEP-2681 details new capabilities to help individual Kubernetes pods to get the correct address for a node. For cloud providers, KEP-3705 provides further improvements for node-ip handling in dual-stack environments.

The LoadBalancer IP mode feature (KEP-1860) is now a beta feature and is enabled by default, allowing specification of load balancer IP behavior in the service status. Additionally, there is a  new alpha feature for service routing preference (KEP-4444) that lets users express preferences for endpoint traffic routing to optimize for proximity, performance, cost or reliability.

The core idea behind Kubernetes is that it is a cloud native platform for deploying, running and scheduling where container workloads run in a cluster.

To that end, one of the big non-networking updates in Kubernetes to take note of is Pod Scheduling Readiness (KEP-3521)

“This now-stable feature lets Kubernetes avoid trying to schedule a Pod that has been defined, when the cluster doesn't yet have the resources provisioned to allow actually binding that Pod to a node,” Kubernetes 1.30 release announcement states. “That's not the only use case; the custom control on whether a Pod can be allowed to schedule also lets you implement quota mechanisms, security controls, and more.”