Breaking changes60(No downgrade1)
Pod resize validation now rejects non-CPU and non-memory resources
Affectspod resize requests
Previously, a resize could add a resource other than CPU or memory when the container had no resources. Now, that request fails with a validation error.
Show release-note lines
- Pod resize now only allows CPU and memory resources; other resource types are forbidden. ([#135084](https://github.com/kubernetes/kubernetes/pull/135084), [@tallclair](https://github.com/tallclair)) [SIG Apps, Node and Testing]
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdHPA configurable tolerance promoted to beta with the HPAConfigurableTolerance gate enabled by default
AffectsHorizontalPodAutoscalers with configurable tolerance settings(Inferred)
The feature was alpha before this release. HPA scaling rules can now use tolerance without separately enabling the gate.
Show release-note lines
- Promoted HPA configurable tolerance to beta. The `HPAConfigurableTolerance` feature gate has now been enabled by default. ([#133128](https://github.com/kubernetes/kubernetes/pull/133128), [@jm-franc](https://github.com/jm-franc)) [SIG API Machinery and Autoscaling]
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdSeparate alpha gate for DeviceTaintRules support
AffectsDRA device taints and tolerations
With the new gate at its default false setting, DeviceTaintRules support is disabled. DRADeviceTaints can remain enabled, so tainting through ResourceSlices continues to work.
Show release-note lines
- The DRA device taints and toleration feature received a separate feature gate, `DRADeviceTaintRules`, which controlled support for `DeviceTaintRules`. This allowed disabling it while keeping `DRADeviceTaints` enabled so that tainting via `ResourceSlices` continued to work. ([#135068](https://github.com/kubernetes/kubernetes/pull/135068), [@pohly](https://github.com/pohly)) [SIG API Machinery, Apps, Auth, Node, Scheduling and Testing]
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdPod status and startup probes stay unchanged on kubelet restart
AffectsPods managed by kubelet(Inferred)
Kubelet restarts could cause Pod status changes.
Show release-note lines
- Added the `ChangeContainerStatusOnKubeletRestart` feature gate, which defaults to disabled. When the feature gate is disabled, `kubelet` does not change the Pod status upon restart, and Pods do not re-run startup probes after the `kubelet` restarts. ([#134746](https://github.com/kubernetes/kubernetes/pull/134746), [@HirazawaUi](https://github.com/HirazawaUi)) [SIG Node and Testing]
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdAPI server SLI metric excludes dryRun request latencies
AffectsAPI-server metric consumers using apiserver_request_sli_duration_seconds with dryRun traffic(Inferred)
Other requests continue to be recorded in the metric.
Show release-note lines
- Metrics: Excluded `dryRun` requests from `apiserver_request_sli_duration_seconds`. ([#131092](https://github.com/kubernetes/kubernetes/pull/131092), [@aldudko](https://github.com/aldudko)) [SIG API Machinery and Instrumentation]
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdHostnameOverride promoted to beta and enabled by default
Affectsworkloads using HostnameOverride(Inferred)
In v1.34, HostnameOverride was alpha and disabled by default.
Show release-note lines
- Promoted the `HostnameOverride` feature gate to beta and enabled it by default. ([#134729](https://github.com/kubernetes/kubernetes/pull/134729), [@HirazawaUi](https://github.com/HirazawaUi)) [SIG Network and Node]
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdkubectl describe pods adds field paths to event messages
Affectspod events with an involved object's fieldPath
Previously, these messages omitted the path; it now appears before the event text.
Show release-note lines
- Updated `kubectl describe pods` to include the involved object’s `fieldPath` (e.g., container name) in event messages, providing better context for debugging multi-container Pods. Note: This changes the previous message format for events that include a `fieldPath`. ([#133627](https://github.com/kubernetes/kubernetes/pull/133627), [@itzPranshul](https://github.com/itzPranshul))
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdDeprecated metrics hidden at policy deadlines
Affectsdeprecated metrics that have reached their policy hiding point(Inferred)
Alpha and Internal metrics are hidden in the minor release they are deprecated; Beta metrics one minor release after their DeprecatedVersion; and Stable metrics three minor releases after their DeprecatedVersion.
Show release-note lines
- Deprecated metrics will be hidden as per the metrics deprecation policy. https://kubernetes.io/docs/reference/using-api/deprecation-policy/#deprecating-a-metric . ([#133436](https://github.com/kubernetes/kubernetes/pull/133436), [@richabanker](https://github.com/richabanker)) [SIG Architecture, Instrumentation and Network]
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdSchedulerAsyncAPICalls disabled by default
AffectsSchedulerAsyncAPICalls enabled in kube-scheduler
Under high kube-apiserver load, asynchronous preemption could degrade kube-scheduler performance; in v1.34, the feature gate was enabled by default.
Show release-note lines
- Disabled the `SchedulerAsyncAPICalls` feature gate to mitigate a bug where its interaction with asynchronous preemption could degrade `kube-scheduler` performance, especially under high `kube-apiserver` load. ([#134400](https://github.com/kubernetes/kubernetes/pull/134400), [@macsko](https://github.com/macsko))
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdUnused DeviceBindingConditions fields dropped when DRADeviceBindingConditions is disabled
AffectsResourceClaims with unused DeviceBindingConditions fields and DRADeviceBindingConditions disabled(Inferred)
Show release-note lines
- Dropped `DeviceBindingConditions` fields when the `DRADeviceBindingConditions` feature gate is not enabled and not in use. ([#134964](https://github.com/kubernetes/kubernetes/pull/134964), [@sunya-ch](https://github.com/sunya-ch))
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdObject-size statistics skipped for resources outside the watch cache
Affectsresources not served from the watch cache, typically Events
In v1.34, key listing for object-size statistics could be expensive and hurt Events POST latency. For events, apiserver_resource_size_estimate_bytes is unavailable, so APF estimates LIST request cost using a 1.5MB fallback and assigns requests maxSeats.
Evidence“* No apiserver_resource_size_estimate_bytes metric for events. * APF overestimating LIST request cost to events. Fallback assumes object size of 1.5MB, meaning LIST events will always get maxSeats” kubernetes/kubernetes/pull/133873 ↗ Show release-note lines
- Kube-apiserver: Fixed a possible `v1.34` performance regression calculating object size statistics for resources not served from the watch cache, typically only `Events`. ([#133873](https://github.com/kubernetes/kubernetes/pull/133873), [@serathius](https://github.com/serathius)) [SIG API Machinery and Etcd]
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdKubelet pod hash generation switched to FNV-1a for empty UIDs
Affectspods with an empty UID that receive kubelet defaults
Previously, applyDefaults generated the hash for pods without a UID using MD5.
Evidence“func applyDefaults(logger klog.Logger, pod *api.Pod, source string, isFile bool, nodeName types.NodeName) error {” kubernetes/kubernetes/pull/133511 ↗ Show release-note lines
- Eliminated and prevented future use of the `md5` algorithm in favor of more appropriate hashing algorithms. ([#133511](https://github.com/kubernetes/kubernetes/pull/133511), [@BenTheElder](https://github.com/BenTheElder)) [SIG Apps, Architecture, CLI, Cluster Lifecycle, Network, Node, Security, Storage and Testing]
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdContainer names removed from created and started event messages
AffectsKubelet events for created and started containers
Previously, these messages included the container name; they now read “Container created” or “Container started.”
Show release-note lines
- Removed container name from messages for container created and started events. ([#134043](https://github.com/kubernetes/kubernetes/pull/134043), [@HirazawaUi](https://github.com/HirazawaUi))
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdKUBECTL_OPENAPIV3_PATCH no longer controls OpenAPI v3 patching
Affectskubectl setups with KUBECTL_OPENAPIV3_PATCH set(Inferred)
Previously, the variable could disable OpenAPI v3 patching. kubectl now attempts to use the OpenAPI v3 client without checking it.
Show release-note lines
- Removed the `KUBECTL_OPENAPIV3_PATCH` environment variable, as aggregated discovery has been stable since `v1.30`. ([#134130](https://github.com/kubernetes/kubernetes/pull/134130), [@ardaguclu](https://github.com/ardaguclu))
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdUser-namespace PSA relaxation is now unconditional
Affectsclusters applying PSA to user-namespace pods or specifying UserNamespacesPodSecurityStandards(Inferred)
Action requiredkubelet v1.31 or later
Previously, the gate prevented PSA policies from being relaxed for user-namespace pods before kubelet support was assured.
Evidence“Now, we can unconditionally relax PSA policy if a pod is in a user namespace.” kubernetes/kubernetes/pull/132157 ↗ Show release-note lines
- Removed the `UserNamespacesPodSecurityStandards` feature gate. The minimum supported Kubernetes version for `kubelet` is now `v1.31`, so the gate is no longer needed. ([#132157](https://github.com/kubernetes/kubernetes/pull/132157), [@haircommander](https://github.com/haircommander)) [SIG Auth, Node and Testing]
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdReferenced-token and secret counts removed from ServiceAccount output
AffectsServiceAccounts viewed with kubectl get or kubectl describe(Inferred)
The human-readable output previously included counts for referenced tokens and secrets; those counts no longer appear.
Show release-note lines
- Updated `kubectl get` and `kubectl describe` human-readable output to no longer show counts for referenced tokens and secrets. ([#117160](https://github.com/kubernetes/kubernetes/pull/117160), [@liggitt](https://github.com/liggitt)) [SIG CLI and Testing]
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdDRA resource.k8s.io storage defaults to v1
No downgradeAffectsclusters using the DRA resource.k8s.io API and its stored resources
Downgrading to 1.33 is not supported.
Show release-note lines
- DRA: the resource.k8s.io API now uses the v1 API version (introduced in 1.34) as default storage version. Downgrading to 1.33 is not supported. ([#133876](https://github.com/kubernetes/kubernetes/pull/133876), [@kei01234kei](https://github.com/kei01234kei)) [SIG API Machinery, Etcd and Testing]
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdkubeadm preflight errors on cgroups v1 with v1.35 or newer kubelets
Affectshosts using cgroups v1 with kubeadm and kubelet v1.35 or newer
Action requiredIgnoring the SystemVerification preflight error and setting failCgroupV1: false in the kube-system/kubelet-config ConfigMap before upgrading
Removed innot stated
The validator previously warned when it detected cgroups v1. From v1.35, failCgroupV1 is set to true, so nodes no longer start on cgroups v1 by default.
Show release-note lines
- ACTION REQUIRED:
vendor: Updated `k8s.io/system-validators` to `v1.12.1`. The cgroups validator now throws an error instead of a warning if cgroups v1 is detected on the host and the provided KubeletVersion is `v1.35` or newer.
kubeadm: Started using `k8s.io/system-validators` `v1.12.1` in `kubeadm` `v1.35`. During `kubeadm init`, `kubeadm join`, and `kubeadm upgrade`, the SystemVerification preflight check throws an error if cgroups v1 is detected and the detected `kubelet` version is `v1.35` or newer. For older versions of `kubelet`, a preflight warning is displayed.
To allow cgroups v1 with `kubeadm` and `kubelet` version `v1.35` or newer, you must:
- Ignore the error from the SystemVerification preflight check by `kubeadm`.
- Edit the `kube-system/kubelet-config` ConfigMap and add the `failCgroupV1: false` field before upgrading. ([#134744](https://github.com/kubernetes/kubernetes/pull/134744), [@neolit123](https://github.com/neolit123)) [SIG Cluster Lifecycle and Node]
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdcgroup v1 nodes blocked from starting by default
Affectsnodes using cgroup v1, especially with kubelet v1.35 or newer
Action requiredFor kubeadm and kubelet v1.35 or newer, allowing cgroup v1 requires ignoring the kubeadm SystemVerification preflight error and adding failCgroupV1: false to the kube-system/kubelet-config ConfigMap before upgrading.
Removed innot stated
Show release-note lines
- ACTION REQUIRED: `failCgroupV1` will be set to true from 1.35.
This means that nodes will not start on a cgroup v1 by default. This puts cgroup v1 into a deprecated state. ([#134298](https://github.com/kubernetes/kubernetes/pull/134298), [@kannon92](https://github.com/kannon92))
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdCore API validation errors gain format-origin metadata
Affectscore API object submissions(Inferred)
When a submitted core API object triggers one of the changed validation checks, its error previously lacked format-origin values; after this release, the error carries metadata such as format=k8s-label-value, and some existing origins use more specific format=... values.
Evidence“+ allErrs = append(allErrs, field.Invalid(path.Index(valueIndex), value, msg)).WithOrigin("format=k8s-label-value")” kubernetes/kubernetes/pull/132825 ↗ Show release-note lines
- Added `WithOrigin` within `apis/core/validation` with adjusted tests. ([#132825](https://github.com/kubernetes/kubernetes/pull/132825), [@PatrickLaabs](https://github.com/PatrickLaabs))
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdStorageVersionMigration API moves from v1alpha1 to v1beta1
Affectsclusters using the StorageVersionMigration v1alpha1 API or containing v1alpha1 resources
v1alpha1 resources could be used before the upgrade; they are no longer supported afterward.
Evidence“Action required: Any use of the v1alpha1 api is no longer supported and users must remove any v1alpha1 resources prior to upgrade.” kubernetes/kubernetes/pull/134784 ↗ Show release-note lines
- Added the `StorageVersionMigration` `v1beta1` API and removed the `v1alpha1` API.
ACTION REQUIRED: The `v1alpha1` API is no longer supported. Users must remove any `v1alpha1` resources before upgrading. ([#134784](https://github.com/kubernetes/kubernetes/pull/134784), [@michaelasp](https://github.com/michaelasp)) [SIG API Machinery, Apps, Auth, Etcd and Testing]
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdDeviceTaintRule drops DeviceClass and CEL selector fields
AffectsDeviceTaintRule resources with DeviceClass or CEL selectors
Evidence“In addition, fields in DeviceTaintRule which cannot be supported properly without more fundamental changes (DeviceClass, CEL selectors) get removed.” kubernetes/kubernetes/pull/134152 ↗ Show release-note lines
- DRA device taints: `DeviceTaintRule` status provides information about the rule, including whether Pods still need to be evicted (`EvictionInProgress` condition). The newly added `None` effect can be used to preview what a `DeviceTaintRule` would do if it used the `NoExecute` effect and to taint devices (`device health`) without immediately affecting scheduling or running Pods. ([#134152](https://github.com/kubernetes/kubernetes/pull/134152), [@pohly](https://github.com/pohly)) [SIG API Machinery, Apps, Auth, Node, Release, Scheduling and Testing]
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdDynamicResourceAllocation locked to enabled for core DRA
Affectssetups configured to disable DynamicResourceAllocation(Inferred)
In v1.34, the gate was enabled by default but was not yet locked to that default.
Show release-note lines
- DRA: The `DynamicResourceAllocation` feature gate for the core functionality (GA in `v1.34`) has now been locked to enabled-by-default and cannot be disabled anymore. ([#134452](https://github.com/kubernetes/kubernetes/pull/134452), [@pohly](https://github.com/pohly)) [SIG Auth, Node, Scheduling and Testing]
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdFeature gates now require enabled dependencies
Affectsfeature-gate configurations that enable features with disabled dependencies, including AllAlpha=true
Action requiredFor configurations using AllAlpha=true, enable the depended-on disabled-by-default beta feature gates with AllBeta=true or by explicitly listing those dependencies; otherwise, the configuration is rejected.
Configurations that enable a feature while its dependency is disabled are rejected at startup, rather than failing silently.
Show release-note lines
- Feature gate dependencies are now explicit, and validated at startup. A feature can no longer be enabled if it depends on a disabled feature. In particular, this means that `AllAlpha=true` will no longer work without enabling disabled-by-default beta features that are depended on (either with `AllBeta=true` or explicitly enumerating the disabled dependencies). ([#133697](https://github.com/kubernetes/kubernetes/pull/133697), [@tallclair](https://github.com/tallclair)) [SIG API Machinery, Architecture, Cluster Lifecycle and Node]
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdDefault gogo protobuf integration removed from Kubernetes API Go types
AffectsGo consumers of Kubernetes API types, especially integrations using the gogo type registry, relying on ProtoMessage(), or using protobuf libraries
Removed inv1.36
Before this release, the types used github.com/gogo/protobuf at runtime, were registered in its global type registry, and implemented ProtoMessage() by default. The marker methods can be restored for one release with the kubernetes_protomessage_one_more_release build tag; they are removed in v1.36.
Show release-note lines
- Kubernetes API Go types removed runtime use of the `github.com/gogo/protobuf` library, and are no longer registered into the global gogo type registry. Kubernetes API Go types were not suitable for use with the `google.golang.org/protobuf` library, and no longer implement `ProtoMessage()` by default to avoid accidental incompatible use. If removal of these marker methods impacts your use, it can be re-enabled for one more release with a `kubernetes_protomessage_one_more_release` build tag, but will be removed in `v1.36`. ([#134256](https://github.com/kubernetes/kubernetes/pull/134256), [@liggitt](https://github.com/liggitt)) [SIG API Machinery, Apps, Architecture, Auth, CLI, Cluster Lifecycle, Instrumentation, Network, Node, Scheduling and Storage]
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdPod observed-generation tracking promoted to GA; feature gate locked to default
Affectsclusters using Pod observed-generation tracking or configuring the PodObservedGenerationTracking feature gate
The feature was beta and default-on in v1.34.
Evidence“+ {Version: version.MustParse("1.35"), Default: true, PreRelease: featuregate.GA, LockToDefault: true}, // GA in 1.35, remove in 1.38” kubernetes/kubernetes/pull/134948 ↗ Show release-note lines
- Promoted `PodObservedGenerationTracking` to GA. ([#134948](https://github.com/kubernetes/kubernetes/pull/134948), [@natasha41575](https://github.com/natasha41575)) [SIG API Machinery, Apps, Node, Scheduling and Testing]
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdJobManagedBy promoted to general availability with its gate locked on
Affectssetups configuring the JobManagedBy feature gate or using Jobs governed by the feature
Removed innot stated
The feature gate can no longer be turned off and is slated for removal in a future Kubernetes release.
Show release-note lines
- Promoted the `JobManagedBy` feature to general availability. The `JobManagedBy` feature gate was locked to `true` and will be removed in a future Kubernetes release. ([#135080](https://github.com/kubernetes/kubernetes/pull/135080), [@dejanzele](https://github.com/dejanzele)) [SIG API Machinery, Apps and Testing]
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdStrictCostEnforcementForVAP and StrictCostEnforcementForWebhooks feature gates removed
Affectssetups configured with StrictCostEnforcementForVAP or StrictCostEnforcementForWebhooks(Inferred)
Both gates had been locked on since v1.32. The release does not describe a change to the enforcement behavior they controlled.
Show release-note lines
- Removed the `StrictCostEnforcementForVAP` and `StrictCostEnforcementForWebhooks` feature gates, which were locked since `v1.32`. ([#134994](https://github.com/kubernetes/kubernetes/pull/134994), [@liggitt](https://github.com/liggitt)) [SIG API Machinery, Auth, Node and Testing]
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdPod Certificates API removed from certificates v1alpha1
Affectsclients, manifests, or automation using the Pod Certificates API in certificates v1alpha1(Inferred)
The API is no longer available in certificates v1alpha1; the beta API is in certificates v1beta1.
Evidence“This PR promotes the Pod Certificates to beta. It also removes the API from the certificates v1alpha1 API group.” kubernetes/kubernetes/pull/134624 ↗ Show release-note lines
- The Pod Certificates feature moved to beta. The `PodCertificateRequest` feature gate is set disabled by default. To use the feature, users must enable the certificates API groups in `v1beta1` and enable the `PodCertificateRequest` feature gate. The `UserAnnotations` field was added to the `PodCertificateProjection` API and the corresponding `UnverifiedUserAnnotations` field was added to the `PodCertificateRequest` API. ([#134624](https://github.com/kubernetes/kubernetes/pull/134624), [@yt2985](https://github.com/yt2985)) [SIG API Machinery, Apps, Auth, Etcd, Instrumentation, Node and Testing]
- Moved the Pod Certificates feature to beta. Added `UserAnnotations` to the `PodCertificateProjection` API and `UnverifiedUserAnnotations` to the `PodCertificateRequest` API. The `PodCertificateRequest` feature gate remains disabled by default and requires enabling the v1beta1 certificates API groups. ([#134790](https://github.com/kubernetes/kubernetes/pull/134790), [@yt2985](https://github.com/yt2985)) [SIG Auth, Instrumentation and Testing]
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdService trafficDistribution preferences reach general availability
AffectsServices using PreferSameZone or PreferSameNode, and clusters configuring the PreferSameTrafficDistribution feature gate
The values were beta in v1.34. The gate already defaulted to true and is now locked to that value.
Show release-note lines
- The `PreferSameZone` and `PreferSameNode` values for the Service
`trafficDistribution` field graduated to general availability. The
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdResourceQuota now counts device class requests in ResourceClaims
AffectsClusters with DRAExtendedResource enabled and ResourceClaims that request device classes
Quota usage is based on the worst-case number of requested devices. It counts against requests.deviceclass.resource.k8s.io/<deviceclass> and, for classes mapped to an extended resource, requests.<extended resource name>.
Show release-note lines
- Updated `ResourceQuota` to count device class requests within a `ResourceClaim` as two additional quotas when the `DRAExtendedResource` feature is enabled:
- `requests.deviceclass.resource.k8s.io/<deviceclass>` is charged based on the worst-case number of devices requested.
- Device classes mapping to an extended resource now consume `requests.<extended resource name>`. ([#134210](https://github.com/kubernetes/kubernetes/pull/134210), [@yliaog](https://github.com/yliaog)) [SIG API Machinery, Apps, Node, Scheduling and Testing]
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdFine-grained supplemental groups policy reaches GA
Affectssetups using the fine-grained supplemental groups policy or configuring its feature gate
In v1.33, the policy was beta and enabled by default. It remains enabled by default, but its feature gate is now locked to that default.
Show release-note lines
- Graduated the fine-grained supplemental groups policy (KEP-3619) to GA. ([#135088](https://github.com/kubernetes/kubernetes/pull/135088), [@everpeace](https://github.com/everpeace)) [SIG Node and Testing]
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdControlPlaneKubeletLocalMode locked on at GA
Affectskubeadm control-plane setups using ControlPlaneKubeletLocalMode or opting out via /etc/kubernetes/kubelet.conf
The gate was already enabled by default while in beta, so its default behavior is unchanged. It is now locked, and opting out requires patching the server field in /etc/kubernetes/kubelet.conf.
Show release-note lines
- Kubeadm: Graduated the kubeadm-specific feature gate `ControlPlaneKubeletLocalMode` to GA and locked it to enabled by default. To opt out, patch the `server` field in `/etc/kubernetes/kubelet.conf`. Deprecated the subphase of `kubeadm join phase control-plane-join` called `etcd`, which is now hidden and replaced by subphase with identical functionality `etcd-join`. The `etcd` subphase will be removed in a future release. The subphase `kubelet-wait-bootstrap` of `kubeadm join` is no longer experimental and will now always run. ([#134106](https://github.com/kubernetes/kubernetes/pull/134106), [@neolit123](https://github.com/neolit123))
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdkubeadm join etcd subphase replaced by etcd-join
Affectsscripts or operators invoking the etcd subphase of kubeadm join phase control-plane-join(Inferred)
Removed innot stated
Invoking etcd no longer runs the phase; etcd-join provides the same functionality.
Show release-note lines
- Kubeadm: Graduated the kubeadm-specific feature gate `ControlPlaneKubeletLocalMode` to GA and locked it to enabled by default. To opt out, patch the `server` field in `/etc/kubernetes/kubelet.conf`. Deprecated the subphase of `kubeadm join phase control-plane-join` called `etcd`, which is now hidden and replaced by subphase with identical functionality `etcd-join`. The `etcd` subphase will be removed in a future release. The subphase `kubelet-wait-bootstrap` of `kubeadm join` is no longer experimental and will now always run. ([#134106](https://github.com/kubernetes/kubernetes/pull/134106), [@neolit123](https://github.com/neolit123))
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdAllowOverwriteTerminationGracePeriodSeconds locked to false
AffectsKubelet setups with a non-default AllowOverwriteTerminationGracePeriodSeconds setting(Inferred)
The gate was introduced in v1.32, when it could be changed from its false default, and was deprecated.
Evidence“This feature gate was added in version v1.32, and no issues have been reported by users within three release versions. Therefore, we can lock it down and prohibit modifications.” kubernetes/kubernetes/pull/133792 ↗ Show release-note lines
- Locked down the `AllowOverwriteTerminationGracePeriodSeconds` feature gate. ([#133792](https://github.com/kubernetes/kubernetes/pull/133792), [@HirazawaUi](https://github.com/HirazawaUi))
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdExecProbeTimeout locked to true
AffectsKubelet configurations that set ExecProbeTimeout to false(Inferred)
The gate was already generally available and defaulted to true, but could previously be set to false. Configurations with that setting are no longer accepted.
Evidence“This is a bug fix so the feature gate will be GA and on by default from the start. Timeline is to lock the feature flag to true in 1.35.” kubernetes/kubernetes/pull/134635 ↗ Show release-note lines
- Locked the (generally available) feature gate `ExecProbeTimeout` to true. ([#134635](https://github.com/kubernetes/kubernetes/pull/134635), [@vivzbansal](https://github.com/vivzbansal)) [SIG Node and Testing]
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdImageGCMaximumAge is stable, with its feature gate locked on
AffectsKubelet configurations using the ImageMaximumGCAge feature gate or imageMaximumGCAge setting(Inferred)
The kubelet uses the configured maximum image-GC age without requiring the feature gate. The gate was already enabled by default, so that default behavior is unchanged.
Evidence“{Version: version.MustParse("1.30"), Default: true, PreRelease: featuregate.Beta}, + {Version: version.MustParse("1.35"), Default: true, PreRelease: featuregate.GA, LockToDefault: true}, // remove in 1.38” kubernetes/kubernetes/pull/134736 ↗ Show release-note lines
- Promoted `ImageGCMaximumAge` to stable. ([#134736](https://github.com/kubernetes/kubernetes/pull/134736), [@haircommander](https://github.com/haircommander)) [SIG Node and Testing]
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdInPlacePodVerticalScaling promoted to GA with its feature gate locked on
Affectssetups using InPlacePodVerticalScaling, especially those setting its feature gate to false(Inferred)
Evidence“{Version: version.MustParse("1.33"), Default: true, PreRelease: featuregate.Beta}, + {Version: version.MustParse("1.35"), Default: true, PreRelease: featuregate.GA, LockToDefault: true}, // remove in 1.38” kubernetes/kubernetes/pull/134949 ↗ Show release-note lines
- Promoted `InPlacePodVerticalScaling` to GA. ([#134949](https://github.com/kubernetes/kubernetes/pull/134949), [@natasha41575](https://github.com/natasha41575)) [SIG API Machinery, Node and Scheduling]
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdkubectl command headers no longer honor the opt-out
Affectskubectl invocations with KUBECTL_COMMAND_HEADERS set to false or zero(Inferred)
Previously, setting KUBECTL_COMMAND_HEADERS to false or zero disabled command headers.
Show release-note lines
- Promoted `kubectl` command headers to stable. ([#134777](https://github.com/kubernetes/kubernetes/pull/134777), [@soltysh](https://github.com/soltysh)) [SIG CLI and Testing]
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdEnvFiles enabled by default as a beta feature
AffectsKubelet workloads using EnvFiles and environment files(Inferred)
In v1.34, the EnvFiles gate was alpha and disabled by default, and the earlier syntax was less restricted. Environment-file syntax is now limited to a subset of POSIX shell syntax, with every variable value enclosed in single quotes.
Show release-note lines
- Promoted the `EnvFiles` feature gate to beta and is enabled by default. Additionally, the syntax specification for environment variables has been restricted to a subset of POSIX shell syntax (all variable values must be wrapped in single quotes). ([#134414](https://github.com/kubernetes/kubernetes/pull/134414), [@HirazawaUi](https://github.com/HirazawaUi)) [SIG Node and Testing]
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdkubectl exec now requires -- before the command
Affectsautomation or commands using kubectl exec(Inferred)
Show release-note lines
- Changed `kubectl exec` syntax to require `--` before the command. The form `kubectl exec [POD] [COMMAND]` is no longer supported; use `kubectl exec [POD] -- [COMMAND]` instead. ([#133841](https://github.com/kubernetes/kubernetes/pull/133841), [@yangjunmyfm192085](https://github.com/yangjunmyfm192085))
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdGenerated ResourceClaim objects no longer set BlockOwnerDeletion
Affectssetups using ResourceClaimTemplate-generated claims or scheduler-created extendedResourceClaim objects
Action requiredan explicit finalizer if the parent must block deletion until the child is deleted
Parent deletion is no longer blocked until these child claims are deleted; that behavior requires an explicit finalizer.
Evidence“If the parent object must block until the child object is deleted, then use an explicit finalizer.” kubernetes/kubernetes/pull/134956 ↗ Show release-note lines
- Removed `BlockOwnerDeletion` from `ResourceClaim` created from `ResourceClaimTemplate` and from `extendedResourceClaim` created by the `scheduler`. ([#134956](https://github.com/kubernetes/kubernetes/pull/134956), [@yliaog](https://github.com/yliaog)) [SIG Apps, Node and Scheduling]
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdkubectl scale missing-resource error format changed
Affectsresource scaling with kubectl
When the specified resource did not exist, kubectl scale previously returned error: no objects passed to scale <GroupResource> "<ResourceName>" not found. It now returns Error from server (NotFound): <GroupResource> "<ResourceName>" not found, matching the format used by commands such as kubectl get.
Evidence“Previously, `kubectl scale` returned the error message `error: no objects passed to scale <GroupResource> "<ResourceName>" not found` when the specified resource did not exist.” kubernetes/kubernetes/pull/134017 ↗ Show release-note lines
- Updated `kubectl scale` to return a consistent error message when a specified resource is not found. Previously, it returned: `error: no objects passed to scale <GroupResource> "<ResourceName>" not found`. It now matches the format used by other commands (e.g., `kubectl get`): `Error from server (NotFound): <GroupResource> "<ResourceName>" not found`. ([#134017](https://github.com/kubernetes/kubernetes/pull/134017), [@mochizuki875](https://github.com/mochizuki875))
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdkubectl describe drops the certificates/v1beta1 fallback
AffectsCertificateSigningRequest resources served through certificates/v1beta1(Inferred)
Previously, kubectl describe tried certificates/v1beta1 if the certificates/v1 lookup failed. Now it returns the error from the certificates/v1 lookup.
Show release-note lines
- Dropped support for `certificates/v1beta1` `CertificateSigningRequest` in `kubectl`. ([#134782](https://github.com/kubernetes/kubernetes/pull/134782), [@scaliby](https://github.com/scaliby))
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdkubectl describe fallback for EndpointSlice removed
AffectsEndpointSlice resources served through discovery/v1beta1(Inferred)
kubectl describe previously tried discovery/v1 first and fell back to discovery/v1beta1 if that lookup failed. Now, a failed discovery/v1 lookup returns an error instead of falling back.
Show release-note lines
- Dropped support for `discovery/v1beta1` `EndpointSlice` in `kubectl`. ([#134913](https://github.com/kubernetes/kubernetes/pull/134913), [@scaliby](https://github.com/scaliby))
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdkubectl describe drops networking/v1beta1 support for IngressClass
Affectskubectl describe on IngressClass resources served through networking/v1beta1(Inferred)
Previously, the describer supported both networking/v1beta1 and networking/v1. Now a failed networking/v1 lookup returns an error instead of falling back to networking/v1beta1.
Evidence“Dropped support for networking/v1beta1 IngressClass in kubectl” kubernetes/kubernetes/pull/135108 ↗ Show release-note lines
- Dropped support for `networking/v1beta1` `Ingress` in `kubectl`. ([#135108](https://github.com/kubernetes/kubernetes/pull/135108), [@scaliby](https://github.com/scaliby))
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdkubectl describe removes the Ingress networking/v1beta1 fallback
AffectsIngress resources served through networking/v1beta1 and described with kubectl describe(Inferred)
Previously, kubectl describe tried networking/v1 first and fell back to networking/v1beta1 if that lookup failed.
Show release-note lines
- Dropped support for `networking/v1beta1` `Ingress` in `kubectl`. ([#135176](https://github.com/kubernetes/kubernetes/pull/135176), [@scaliby](https://github.com/scaliby))
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdkubectl describe drops policy/v1beta1 PodDisruptionBudget fallback
Affectskubectl describe use for PodDisruptionBudget resources served through policy/v1beta1(Inferred)
Previously, a NotFound from the policy/v1 lookup triggered a fallback to policy/v1beta1.
Evidence“Dropped support for policy/v1beta1 PodDisruptionBudget in kubectl” kubernetes/kubernetes/pull/134685 ↗ Show release-note lines
- Dropped support for `policy/v1beta1` PodDisruptionBudget in kubectl. ([#134685](https://github.com/kubernetes/kubernetes/pull/134685), [@scaliby](https://github.com/scaliby))
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdHashObject removed from the kubectl utility package
AffectsGo code importing k8s.io/kubectl/pkg/util and calling HashObject(Inferred)
Before this release, it encoded an object and returned its MD5 hash.
Evidence“// HashObject returns the hash of a Object hash by a Codec” kubernetes/kubernetes/pull/133511 ↗ Show release-note lines
- Eliminated and prevented future use of the `md5` algorithm in favor of more appropriate hashing algorithms. ([#133511](https://github.com/kubernetes/kubernetes/pull/133511), [@BenTheElder](https://github.com/BenTheElder)) [SIG Apps, Architecture, CLI, Cluster Lifecycle, Network, Node, Security, Storage and Testing]
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdKubelet removes --pod-infra-container-image flag
AffectsKubelet configurations using --pod-infra-container-image, including kubeadm extraArgs
Action requiredRemove --pod-infra-container-image from non-kubeadm kubelet configuration and, for kubeadm, from extraArgs in the kubelet configuration file.
The flag had been applied by kubeadm even though its function had moved to CRI. A retained flag can cause kubelet startup failures after the upgrade.
Show release-note lines
- Kubeadm: stopped applying the `--pod-infra-container-image` flag for the kubelet. The flag has been deprecated and no longer served a purpose in the kubelet as the logic was migrated to CRI (Container Runtime Interface). During upgrade, kubeadm will attempt to remove the flag from the file `/var/lib/kubelet/kubeadm-flags.env`. ([#133778](https://github.com/kubernetes/kubernetes/pull/133778), [@carlory](https://github.com/carlory)) [SIG Cloud Provider and Cluster Lifecycle]
- ACTION REQUIRED:
Removed the `--pod-infra-container-image` flag from `kubelet` command line. For `non-kubeadm` clusters, users must manually remove this flag from their `kubelet` configuration to prevent startup failures before upgrading `kubelet`. For `kubeadm` clusters, if users pass extra arguments to the `kubelet` like `--pod-infra-container-image`, it will be written to the `kubelet` env file during the `init` phase. `kubeadm` does not remove it during the `init` or `join` phase, so users must manually remove it from `extraArgs` in the `kubelet` configuration file. ([#133779](https://github.com/kubernetes/kubernetes/pull/133779), [@carlory](https://github.com/carlory))
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdScheduler framework types moved to k8s.io/kube-scheduler/framework
AffectsGo code and scheduler plugins importing the listed types from k/k/pkg/scheduler/framework
Action requiredUsers of the moved types should update their import paths to k8s.io/kube-scheduler/framework.
The interfaces remain unchanged.
Show release-note lines
- Moved Types in `k/k/pkg/scheduler/framework`:
`Handle`,
`Plugin`,
`PreEnqueuePlugin`, `QueueSortPlugin`, `EnqueueExtensions`, `PreFilterExtensions`, `PreFilterPlugin`, `FilterPlugin`, `PostFilterPlugin`, `PreScorePlugin`, `ScorePlugin`, `ReservePlugin`, `PreBindPlugin`, `PostBindPlugin`, `PermitPlugin`, `BindPlugin`,
`PodActivator`, `PodNominator`, `PluginsRunner`,
`LessFunc`, `ScoreExtensions`, `NodeToStatusReader`, `NodeScoreList`, `NodeScore`, `NodePluginScores`, `PluginScore`, `NominatingMode`, `NominatingInfo`, `WaitingPod`, `PreFilterResult`, `PostFilterResult`,
`Extender`,
`NodeInfoLister`, `StorageInfoLister`, `SharedLister`, `ResourceSliceLister`, `DeviceClassLister`, `ResourceClaimTracker`, `SharedDRAManager`
to package `k8s.io/kube-scheduler/framework`. Users should update import paths. The interfaces don't change.
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdScheduler Parallelizer interface moved to staging package
AffectsGo code importing the Parallelizer interface from k/k/pkg/scheduler/framework/parallelism(Inferred)
Action requiredParallelizer interface imports use k8s.io/kube-scheduler/framework
The Parallelizer struct remains in its existing location in k/k.
Show release-note lines
Type `Parallelizer` in `k/k/pkg/scheduler/framework/parallelism` has been split into interface `Parallelizer` (in `k8s.io/kube-scheduler/framework`) and `struct Parallelizer` (location unchanged in k/k). Plugin developers should update the import path to staging repo. ([#133172](https://github.com/kubernetes/kubernetes/pull/133172), [@ania-borowiec](https://github.com/ania-borowiec)) [SIG Node, Release, Scheduling, Storage and Testing]
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdDRA protocol definitions switch from gogo to standard protobuf
AffectsCode or components using the DRA protocol definitions in k8s.io/kubelet/pkg/apis/dra(Inferred)
The package's old definitions used gogo; the new ones use standard protoc/google.golang.org/protobuf definitions.
Evidence“Use standard protoc for the dra instead of gogo.” kubernetes/kubernetes/pull/133026 ↗ Show release-note lines
- Removed deprecated gogo protocol definitions from `k8s.io/kubelet/pkg/apis/dra` in favor of `google.golang.org/protobuf`. ([#133026](https://github.com/kubernetes/kubernetes/pull/133026), [@saschagrunert](https://github.com/saschagrunert)) [SIG API Machinery and Node]
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdSizeMemoryBackedVolumes feature gate removed
AffectsKubelet configurations with the SizeMemoryBackedVolumes feature gate(Inferred)
The gate had been enabled by default and locked to that setting since 1.32; memory-backed emptyDir sizing now applies without checking it.
Evidence“This cleans up SizeMemoryBackedVolumes feature gate after it was graduated to stable back in 1.32.” kubernetes/kubernetes/pull/133720 ↗ Show release-note lines
- Removed general available feature-gate `SizeMemoryBackedVolumes`. ([#133720](https://github.com/kubernetes/kubernetes/pull/133720), [@carlory](https://github.com/carlory)) [SIG Node, Storage and Testing]
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdComponentSLIs feature gate removed
Affectssetups that specify the ComponentSLIs feature gate(Inferred)
The gate was present in the prior release; the feature had been stable since Kubernetes v1.32.
Show release-note lines
- Removed the `ComponentSLIs` feature gate, as it was promoted to stable in the Kubernetes `v1.32` release. ([#133742](https://github.com/kubernetes/kubernetes/pull/133742), [@carlory](https://github.com/carlory)) [SIG Architecture and Instrumentation]
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdstorage.k8s.io/v1alpha1 VolumeAttributesClass API no longer served
Affectsclients or manifests using storage.k8s.io/v1alpha1 VolumeAttributesClass(Inferred)
Evidence“The storage.k8s.io/v1alpha1 VolumeAttributesClass API is no longer served in 1.35” kubernetes/kubernetes/pull/134625 ↗ Show release-note lines
- Removed the `VolumeAttributesClass` resource from the `storage.k8s.io/v1alpha1` API in `v1.35`. ([#134625](https://github.com/kubernetes/kubernetes/pull/134625), [@liggitt](https://github.com/liggitt)) [SIG API Machinery, Etcd, Storage and Testing]
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdAggregated discovery v2beta1 type removed
AffectsAPI server configurations using AggregatedDiscoveryRemoveBetaType or the aggregated discovery v2beta1 type(Inferred)
Removed innot stated
The AggregatedDiscoveryRemoveBetaType gate is deprecated and locked to true.
Show release-note lines
- The `AggregatedDiscoveryRemoveBetaType` feature gate was deprecated and locked to `true`. ([#134230](https://github.com/kubernetes/kubernetes/pull/134230), [@Jefftree](https://github.com/Jefftree))
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdSystemdWatchdog feature gate locked to its default
AffectsKubelet systemd watchdog integration or SystemdWatchdog feature-gate configuration
Removed inv1.37
Kubelet systemd watchdog functionality can be enabled through systemd without configuring the feature gate.
Show release-note lines
- The `SystemdWatchdog` feature gate has been locked to default and will be removed in future release. The systemd watchdog functionality in `kubelet` can be enabled via systemd without any feature gate configuration. See the [systemd watchdog documentation](https://kubernetes.io/docs/reference/node/systemd-watchdog/) for more information. ([#134691](https://github.com/kubernetes/kubernetes/pull/134691), [@SergeyKanzhelev](https://github.com/SergeyKanzhelev))
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdkubeadm WaitForAllControlPlaneComponents gate removed
Affectskubeadm configurations that specify WaitForAllControlPlaneComponents(Inferred)
The gate was already locked to enabled by default in v1.34.
Show release-note lines
- `kubeadm`: Removed the `WaitForAllControlPlaneComponents` feature gate, which graduated to GA in `v1.34` and was locked to enabled by default. ([#134781](https://github.com/kubernetes/kubernetes/pull/134781), [@neolit123](https://github.com/neolit123))
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.mdkubeadm raises the minimum supported external etcd version
Affectskubeadm setups using external etcd with control plane versions v1.32, v1.33, or v1.34
The minimum supported external etcd version was 3.5.23-0; it is now 3.5.24-0.
Show release-note lines
- `kubeadm`: Updated the supported etcd version to `v3.5.24` for control plane versions `v1.32`, `v1.33`, and `v1.34`. ([#134779](https://github.com/kubernetes/kubernetes/pull/134779), [@joshjms](https://github.com/joshjms)) [SIG API Machinery, Cloud Provider, Cluster Lifecycle, Etcd and Testing]
github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.md