Kubernetes 1.31 Release Notes

Indexes

• New and Enhanced Features
• API Changes and Removals
• Enhanced Kubernetes 1.31 on CCE
• References

New and Enhanced Features

• Start ordinal of StatefulSets is in the General Availability (GA) state.

  StatefulSet start ordinal is advanced to GA. By default, each pod in a StatefulSet is assigned an integer ordinal from 0. With this feature, you can configure a start ordinal for each pod. For details, see Start ordinal.

• Elastic indexed jobs are in the GA state.

  Elastic indexed jobs are advanced to GA. You can scale indexed Jobs up or down by modifying .spec.completions and .spec.parallelism. For details, see Elastic Indexed Jobs.

• Pod failure policy is in the GA state.

  Pod failure policies are advanced to GA. This feature allows you to choose how the system handles pod failures by specifying the processing mode (retry or ignore). This helps prevent unnecessary pod restarts. For details, see Pod failure policy.

• Pod disruption conditions are in the GA state.

  Pod disruption conditions are advanced to GA. The new DisruptionTarget condition indicates the reasons for pod failures, such as being preempted by a higher priority pod, cleared due to node deletion, or terminated by kubelet. When a pod is created using a job or cron job, you can use these pod disruption conditions as part of your job's pod failure policy to define the action when a pod is abnormal. For details, see Pod disruption conditions.

• Selectable fields for custom resources are in the beta state.

  Selectable fields for custom resources are moved to beta. You can specify the selectableFields field of a CustomResourceDefinition (CRD) to define which other fields in a custom resource may be used in field selectors. Field selectors can then be used to get only resources by filtering List, Watch, and DeleteCollection requests. For details, see Selectable fields for custom resources.

• Job success policies are in the beta state.

  Job success policies are moved to beta. This feature allows you to configure success policies for jobs based on the number of pods that succeeded. For details, see Success policy.

• matchLabelKeys is in the beta state.

  matchLabelKeys is moved to beta. matchLabelKeys and mismatchLabelKeys are finer fields for pod affinity or anti-affinity. They specify the keys for the labels that should or should not match with the incoming pod's labels, so that a rolling upgrade will not break affinity or anti-affinity. For details, see matchLabelKeys.

• ServiceAccountTokenNodeBinding is in the beta state.

  ServiceAccountTokenNodeBinding is moved to beta. You can create a service account token that is directly bound to a node. The token defines the node information and verifies whether the node is available. The token will be valid until it expires or either the associated node is deleted. For details, see Manually create an API token for a ServiceAccount.

API Changes and Removals

• In Kubernetes 1.31, the kubectl exec [POD] [COMMAND] command cannot be executed without a -- separator. In this case, you need to run kubectl exec [POD] -- [COMMAND].
• In Kubernetes 1.31, if caBundle is not empty but the value is invalid or it does not define any CA certificate, the CRD does not provide services. If caBundle is set to a valid value, it remains unchanged if updated. Attempting direct updates results in an "invalid field value" error, ensuring uninterrupted CRD services.

Enhanced Kubernetes 1.31 on CCE

References