Container Engine for Kubernetes now supports Kubernetes version 1.30.1, in addition to versions 1.29.1 and 1.28.2. Oracle recommends you upgrade your Kubernetes environment to version 1.30.1. For more information about Kubernetes 1.30.1, see the Kubernetes Changelog.

Note that Container Engine for Kubernetes support for Kubernetes version 1.30.1 introduces changes to default Container Engine for Kubernetes behavior with regards CPU and memory reservation. On clusters running Kubernetes version 1.30.1 and later, CPU and memory resources for managed nodes are reserved by default, using the --kube-reserved and --system-reserved kubelet flags respectively (as recommended in Best Practice: Reserve resources for Kubernetes and OS system daemons). As a result, on clusters running Kubernetes version 1.30.1 and later, there is a difference between a node's total resources, and the resources that are available for workloads to request. For more information, see Best Practice: Reserve resources for Kubernetes and OS system daemons.

Also note the following:

• With the availability of support for Kubernetes version 1.30.1, Container Engine for Kubernetes will cease support for Kubernetes versions 1.27.10 on August 15, 2024. As a result, you will no longer be able to:
  • Create new clusters running Kubernetes versions 1.27.10.
  • Add new node pools to existing clusters running Kubernetes versions 1.27.10.
• If you currently have existing clusters running Kubernetes version 1.27.10 or earlier, Oracle strongly recommends you immediately upgrade those clusters to Kubernetes versions 1.30.1, 1.29.1, or 1.28.2. You can upgrade control plane nodes through unsupported minor versions. Kubernetes requires that you upgrade control plane nodes one minor version at a time. For example, if a control plane node is running Kubernetes version 1.26.7 (an unsupported minor version), you must upgrade it to Kubernetes version 1.27.10 (also an unsupported minor version), before upgrading it to 1.28.2.
• Clusters that are not upgraded will continue to function as expected. However, they will no longer be supported.

To upgrade a cluster to a new Kubernetes minor version:

1. Upgrade the Kubernetes version running on the control plane by following the instructions in Upgrading the Kubernetes Version on Control Plane Nodes in a Cluster.
2. Having upgraded the control plane, upgrade the Kubernetes version running on worker nodes in a node pool by following the instructions in Upgrading the Kubernetes Version on Worker Nodes in a Cluster.

Note:

Always follow the Kubernetes skew policy for Kubernetes minor version support. Note that in Kubernetes version 1.28, the Kubernetes skew policy expanded. Prior to Kubernetes version 1.28, the skew policy required a cluster's control plane nodes to be no more than two versions ahead of worker nodes. From Kubernetes version 1.28, the Kubernetes skew policy allows control plane nodes to be up to three versions ahead of worker nodes.

Example skew policy:

• Kubernetes control plane nodes are at version 1.30.1
• Kubernetes worker nodes must be at version 1.30.1, 1.29.1, 1.28.2, or 1.27.10

Note that although the worker nodes in a node pool must follow the Kubernetes skew policy, you do not have to upgrade them one minor version at a time.

For more information, see Upgrading Clusters to Newer Kubernetes Versions.