|
| 1 | +--- |
| 2 | +layout: blog |
| 3 | +draft: true |
| 4 | +title: 'Kubernetes v1.34 Sneak Peek' |
| 5 | +date: 2025-07-28 |
| 6 | +slug: kubernetes-v1-34-sneak-peek |
| 7 | +author: > |
| 8 | + Agustina Barbetta, |
| 9 | + Alejandro Josue Leon Bellido, |
| 10 | + Graziano Casto, |
| 11 | + Melony Qin, |
| 12 | + Dipesh Rawat |
| 13 | +--- |
| 14 | + |
| 15 | +Kubernetes v1.34 is coming at the end of August 2025. This release will not include any removal or deprecation, but it is packed with an impressive number of enhancements. Here are some of the features we are most excited about in this cycle! |
| 16 | + |
| 17 | +Please note that this information reflects the current state of v1.34 development and may change before release. |
| 18 | + |
| 19 | +## Featured enhancements of Kubernetes v1.34 |
| 20 | + |
| 21 | +The following list highlights some of the notable enhancements likely to be included in the v1.34 release, but is not an exhaustive list of all planned changes. This is not a commitment and the release content is subject to change. |
| 22 | + |
| 23 | +### The core of DRA targets stable |
| 24 | + |
| 25 | +[Dynamic Resource Allocation](/docs/concepts/scheduling-eviction/dynamic-resource-allocation/) (DRA) provides a flexible way to categorize, request, and use devices like GPUs or custom hardware in your Kubernetes cluster. |
| 26 | + |
| 27 | +Since the v1.30 release, DRA has been based around claiming devices using _structured parameters_ that are opaque to the core of Kubernetes. |
| 28 | +The relevant enhancement proposal, [KEP-4381](https://kep.k8s.io/4381), took inspiration from dynamic provisioning for storage volumes. |
| 29 | +DRA with structured parameters relies on a set of supporting API kinds: ResourceClaim, DeviceClass, ResourceClaimTemplate, and ResourceSlice API types under `resource.k8s.io`, while extending the `.spec` for Pods with a new `resourceClaims` field. |
| 30 | +The core of DRA is targeting graduation to stable in Kubernetes v1.34. |
| 31 | + |
| 32 | + |
| 33 | +With DRA, device drivers and cluster admins define device classes that are available for use. Workloads can claim devices from a device class within device requests. Kubernetes allocates matching devices to specific claims and places the corresponding Pods on nodes that can access the allocated devices. This framework provides flexible device filtering using CEL, centralized device categorization, and simplified Pod requests, among other benefits. |
| 34 | + |
| 35 | +Once this feature has graduated, the `resource.k8s.io/v1` APIs will be available by default. |
| 36 | + |
| 37 | +### ServiceAccount tokens for image pull authentication |
| 38 | + |
| 39 | +The [ServiceAccount](/docs/concepts/security/service-accounts/) token integration for `kubelet` credential providers is likely to reach beta and be enabled by default in Kubernetes v1.34. You'll then be able to have the `kubelet` use these tokens when pulling container images from registries that require authentication. |
| 40 | + |
| 41 | +That support already exists as alpha, and is tracked as part of [KEP-4412](https://kep.k8s.io/4412). |
| 42 | + |
| 43 | +The existing alpha integration allows the `kubelet` to use short-lived, automatically rotated ServiceAccount tokens (that follow OIDC-compliant semantics) to authenticate to a container image registry. Each token is scoped to one associated Pod; the overall mechanism replaces the need for long-lived image pull Secrets. |
| 44 | + |
| 45 | +Adopting this new approach reduces security risks, supports workload-level identity, and helps cut operational overhead. It brings image pull authentication closer to modern, identity-aware good practice. |
| 46 | + |
| 47 | +### Pod replacement policy for Deployments |
| 48 | + |
| 49 | +After a change to a [Deployment](/docs/concepts/workloads/controllers/deployment/), terminating pods may stay up for a considerable amount of time and may consume additional resources. |
| 50 | +As part of [KEP-3973](https://kep.k8s.io/3973), the `.spec.podReplacementPolicy` field will be introduced (as alpha) for Deployments. |
| 51 | + |
| 52 | +If your cluster has the feature enabled, you'll be able to select one of two policies: |
| 53 | + |
| 54 | +`TerminationStarted` |
| 55 | +: Creates new pods as soon as old ones start terminating, resulting in faster rollouts at the cost of potentially higher resource consumption. |
| 56 | + |
| 57 | +`TerminationComplete` |
| 58 | +: Waits until old pods fully terminate before creating new ones, resulting in slower rollouts but ensuring controlled resource consumption. |
| 59 | + |
| 60 | +This feature makes Deployment behavior more predictable by letting you choose when new pods should be created during updates or scaling. It's beneficial when working in clusters with tight resource constraints or with workloads with long termination periods. |
| 61 | + |
| 62 | +It’s expected to be available as an alpha feature and can be enabled using the `DeploymentPodReplacementPolicy` and `DeploymentReplicaSetTerminatingReplicas` feature gates in the API server and kube-controller-manager. |
| 63 | + |
| 64 | +### Production-ready tracing for `kubelet` and API Server |
| 65 | + |
| 66 | +To address the longstanding challenge of debugging node-level issues by correlating disconnected logs, [KEP-2831](https://kep.k8s.io/2831) provides deep, contextual insights into the `kubelet`. |
| 67 | + |
| 68 | +This feature instruments the `kubelet`'s critical operations, particularly its gRPC calls to the Container Runtime Interface (CRI), using the vendor-agnostic OpenTelemetry standard. It allows operators to visualize the entire lifecycle of events (for example: a Pod startup) to pinpoint sources of latency and errors. Its most powerful aspect is the propagation of trace context; the `kubelet` passes a trace ID with its requests to the container runtime, enabling runtimes to link their own spans. |
| 69 | + |
| 70 | +This effort is complemented by a parallel enhancement, [KEP-647](https://kep.k8s.io/647), which brings the same tracing capabilities to the Kubernetes API server. Together, these enhancements provide a more unified, end-to-end view of events, simplifying the process of pinpointing latency and errors from the control plane down to the node. These features have matured through the official Kubernetes release process. [KEP-2831](https://kep.k8s.io/2831) was introduced as an alpha feature in v1.25, while [KEP-647](https://kep.k8s.io/647) debuted as alpha in v1.22. Both enhancements were promoted to beta together in the v1.27 release. Looking forward, Kubelet Tracing ([KEP-2831](https://kep.k8s.io/2831)) and API Server Tracing ([KEP-647](https://kep.k8s.io/647)) are now targeting graduation to stable in the upcoming v1.34 release. |
| 71 | + |
| 72 | +### `PreferSameZone` and `PreferSameNode` traffic distribution for Services |
| 73 | + |
| 74 | +The `spec.trafficDistribution` field within a Kubernetes [Service](/docs/concepts/services-networking/service/) allows users to express preferences for how traffic should be routed to Service endpoints. |
| 75 | + |
| 76 | +[KEP-3015](https://kep.k8s.io/3015) deprecates `PreferClose` and introduces two additional values: `PreferSameZone` and `PreferSameNode`. `PreferSameZone` is equivalent to the current `PreferClose`. `PreferSameNode` prioritizes sending traffic to endpoints on the same node as the client. |
| 77 | + |
| 78 | +This feature was introduced in v1.33 behind the `PreferSameTrafficDistribution` feature gate. It is targeting graduation to beta in v1.34 with its feature gate enabled by default. |
| 79 | + |
| 80 | +### Support for KYAML: a Kubernetes dialect of YAML |
| 81 | + |
| 82 | +KYAML aims to be a safer and less ambiguous YAML subset, and was designed specifically |
| 83 | +for Kubernetes. Whatever version of Kubernetes you use, you'll be able use KYAML for writing manifests |
| 84 | +and/or Helm charts. |
| 85 | +You can write KYAML and pass it as an input to **any** version of `kubectl`, |
| 86 | +because all KYAML files are also valid as YAML. |
| 87 | +With kubectl v1.34, we expect you'll also be able to request KYAML output from `kubectl` (as in `kubectl get -o kyaml …`). |
| 88 | +Of course, you can still request JSON or YAML output if you prefer that. |
| 89 | + |
| 90 | +KYAML addresses specific challenges with both YAML and JSON. YAML's significant whitespace requires careful attention to indentation and nesting, while its optional string-quoting can lead to unexpected type coercion (for example: ["The Norway Bug"](https://hitchdev.com/strictyaml/why/implicit-typing-removed/)). Meanwhile, JSON lacks comment support and has strict requirements for trailing commas and quoted keys. |
| 91 | + |
| 92 | +[KEP-5295](https://kep.k8s.io/5295) introduces KYAML, which tries to address the most significant problems by: |
| 93 | + |
| 94 | +* Always double-quoting value strings |
| 95 | + |
| 96 | +* Leaving keys unquoted unless they are potentially ambiguous |
| 97 | + |
| 98 | +* Always using `{}` for mappings (associative arrays) |
| 99 | + |
| 100 | +* Always using `[]` for lists |
| 101 | + |
| 102 | +This might sound a lot like JSON, because it is! But unlike JSON, KYAML supports comments, allows trailing commas, and doesn't require quoted keys. |
| 103 | + |
| 104 | +We're hoping to see KYAML introduced as a new output format for `kubectl` v1.34. |
| 105 | +As with all these features, none of these changes are 100% confirmed; watch this space! |
| 106 | + |
| 107 | +As a format, KYAML is and will remain a **strict subset of YAML**, ensuring that any compliant YAML parser can parse KYAML documents. Kubernetes does not insist you provide input that is specifically formatted as KYAML, and we have no plan to change that. |
| 108 | + |
| 109 | +### Fine-grained autoscaling control with HPA configurable tolerance |
| 110 | + |
| 111 | +[KEP-4951](https://kep.k8s.io/4951) introduces a new feature that allows users to configure autoscaling tolerance on a per-HPA basis, overriding the default cluster-wide 10% tolerance setting that often proves too coarse-grained for diverse workloads. The enhancement adds an optional `tolerance` field to the HPA's `spec.behavior.scaleUp` and `spec.behavior.scaleDown` sections, enabling different tolerance values for scale-up and scale-down operations, which is particularly valuable since scale-up responsiveness is typically more critical than scale-down speed for handling traffic surges. |
| 112 | + |
| 113 | +Released as alpha in Kubernetes v1.33 behind the `HPAConfigurableTolerance` feature gate, this feature is expected to graduate to beta in v1.34. |
| 114 | +This improvement helps to address scaling challenges with large deployments, where for scaling in, |
| 115 | +a 10% tolerance might mean leaving hundreds of unnecessary Pods running. |
| 116 | +Using the new, more flexible approach would enable workload-specific optimization for both |
| 117 | +responsive and conservative scaling behaviors. |
| 118 | + |
| 119 | +## Want to know more? |
| 120 | +New features and deprecations are also announced in the Kubernetes release notes. We will formally announce what's new in [Kubernetes v1.34](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.34.md) as part of the CHANGELOG for that release. |
| 121 | + |
| 122 | +The Kubernetes v1.34 release is planned for **Wednesday 27th August 2025**. Stay tuned for updates! |
| 123 | + |
| 124 | +## Get involved |
| 125 | +The simplest way to get involved with Kubernetes is by joining one of the many [Special Interest Groups](https://github.com/kubernetes/community/blob/master/sig-list.md) (SIGs) that align with your interests. Have something you’d like to broadcast to the Kubernetes community? Share your voice at our weekly [community meeting](https://github.com/kubernetes/community/tree/master/communication), and through the channels below. Thank you for your continued feedback and support. |
| 126 | + |
| 127 | +* Follow us on Bluesky [@kubernetes.io](https://bsky.app/profile/kubernetes.io) for the latest updates |
| 128 | +* Join the community discussion on [Discuss](https://discuss.kubernetes.io/) |
| 129 | +* Join the community on [Slack](http://slack.k8s.io/) |
| 130 | +* Post questions (or answer questions) on [Server Fault](https://serverfault.com/questions/tagged/kubernetes) or [Stack Overflow](http://stackoverflow.com/questions/tagged/kubernetes) |
| 131 | +* Share your Kubernetes [story](https://docs.google.com/a/linuxfoundation.org/forms/d/e/1FAIpQLScuI7Ye3VQHQTwBASrgkjQDSS5TP0g3AXfFhwSM9YpHgxRKFA/viewform) |
| 132 | +* Read more about what’s happening with Kubernetes on the [blog](https://kubernetes.io/blog/) |
| 133 | +* Learn more about the [Kubernetes Release Team](https://github.com/kubernetes/sig-release/tree/master/release-team) |
0 commit comments