CCE Release of Kubernetes v1_26 History
Updated at:2025-10-27
Baidu AI Cloud Container Engine (CCE) fully complies with community conformance certification. This document highlights the key changes introduced in Kubernetes 1.26 by CCE compared to version 1.24.
Resource changes and deprecations
- flowcontrol.apiserver.k8s.io/v1beta1 is deprecated. Starting from Kubernetes 1.26, you can use flowcontrol.apiserver.k8s.io/v1beta3
- autoscaling/v2beta1 and autoscaling/v2beta2 are deprecated in Kubernetes 1.25 and 1.26 respectively. Starting from Kubernetes 1.23, you can use autoscaling/v2
- batch/v1beta1 is deprecated. Starting from Kubernetes 1.21, you can use batch/v1
-
discovery.k8s.io/v1beta1 is deprecated. Starting from Kubernetes 1.21, you can use discovery.k8s.io/v1. Key changes to note in discovery.k8s.io/v1 are:
- Use the NodeName field of each Endpoint instead of the deprecated topology [“kubernetes.io/hostname”] field.
- Use the Zone field of each Endpoint instead of the deprecated topology["kubernetes.io/zone"] field.
- The Topology field has been replaced with deprecatedTopology, and it is not writable in the v1 version of the API.
-
events.k8s.io/v1beta1 is deprecated. Starting from Kubernetes 1.19, you can use events.k8s.io/v1. Key changes to note in events.k8s.io/v1 are:
- The type field can only be set to either Normal or Warning;
- The involvedObject field is renamed to regarding;
- The action, reason, reportingController, and reportingInstance fields are all required when creating a new Event of the events.k8s.io/v1 version;
- Use eventTime instead of the deprecated firstTimestamp field (this field has been renamed to deprecatedFirstTimestamp and is not allowed in new events.k8s.io/v1 Event objects);
- Use series.lastObservedTime instead of the deprecated lastTimestamp field (this field has been renamed to deprecatedLastTimestamp and is not allowed in new events.k8s.io/v1 Event objects);
- Use series.count instead of the deprecated count field (this field has been renamed to deprecatedCount and is not allowed in new events.k8s.io/v1 Event objects);
- Use reportingController instead of the deprecated source.component field (this field has been renamed to deprecatedSource.component and is not allowed in new events.k8s.io/v1 Event objects);
- Use the reportingInstance field instead of the deprecated source.host field (which has been renamed to deprecatedSource.host and is not accepted in new events.k8s.io/v1 Event objects).
- autoscaling/v2beta1 is deprecated. Starting from Kubernetes 1.23, you can use autoscaling/v2
-
policy/v1beta1 is deprecated. Starting from Kubernetes 1.21, you can use policy/v1. Key changes to note in policy/v1 are:
- In the policy/v1 version of PodDisruptionBudget, setting spec.selector to an empty value ({}) will select all pods in the namespace (whereas in policy/v1beta1, an empty spec.selector did not select any pods). If spec.selector is left unset, no pods will be selected in either API version.
- node.k8s.io/v1beta1 is deprecated. Starting from Kubernetes 1.20, you can use node.k8s.io/v1
Other changes and deprecations
- Deprecate PodSecurityPolicy: Starting from Kubernetes 1.25, the PodSecurityPolicy in the policy/v1beta1 API version is no longer available;
- Deprecate TopologyKeys: The topologyKeys field in Service is deprecated;
- RuntimeClass has been deprecated: Starting from version 1.25, the RuntimeClass in the node.k8s.io/v1beta1 API version is no longer supported.
- PodSecurityPolicy has entered the deprecation phase as of version 1.21 and is expected to be fully removed in version 1.25.
Reference link
For a detailed comparison between Kubernetes 1.26 and other versions, please refer to:
