Support for Kubernetes version 1.36.1

OCI Kubernetes Engine (OKE) now supports Kubernetes version 1.36.1, in addition to versions 1.35.2 and 1.34.2. With the availability of support for Kubernetes version 1.36.1, OKE will cease support for Kubernetes version 1.33.10 on August 10, 2026. Oracle strongly recommends you immediately upgrade clusters to Kubernetes version 1.34.2, 1.35.2, or 1.36.1. For more information about Kubernetes version 1.36.1, see the Kubernetes Changelog.

Note the following:

• Although Kubernetes version 1.33.10 will not be supported after August 10, 2026, it might continue to be available for selection. However, Oracle strongly recommends you upgrade clusters to Kubernetes version 1.34.2, 1.35.2, or 1.36.1.

• New clusters that you create with OKE to run Kubernetes version 1.36.1 or later use Kubernetes Key Management Service (KMS) provider version 2 for Kubernetes secret objects from the time the cluster is created.

  When you upgrade an existing cluster that uses a master encryption key you manage to Kubernetes version 1.36.1 or later, OKE starts using KMS provider version 2 for new Kubernetes secret objects and for existing secret objects that are subsequently updated. Existing unchanged secret objects can remain encrypted using KMS provider version 1. OKE retains KMS provider version 1 as a read fallback and does not automatically migrate all existing secret objects.

  To re-encrypt all existing unchanged Kubernetes secret objects using KMS provider version 2, see Migrating Kubernetes Secrets to KMS v2.

• For worker nodes in clusters running Kubernetes version 1.35 (and later), Kubernetes Engine supports OKE OL8 images, and custom images based on OKE OL8 images. Custom images based on OL8 platform images are also supported, but only if you enable cgroups v2 (see Enabling Cgroups v2 on OL8 Worker Nodes Using Custom Images).

  In clusters running Kubernetes version 1.35 (and later), the use of platform images (both OL7 platform images and OL8 platform images) is not recommended. We strongly recommend the use of OKE images for all new deployments and upgrades. If you want to continue to use a platform image, create a custom image based on the platform image and specify the custom image's OCID when creating or updating a node pool (note that we do not recommend this approach).

  For more information, see Notes about Kubernetes version 1.35 (and later) and Support for OKE Images, Platform Images, and Custom Images.

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.36.1
• Kubernetes worker nodes must be at version 1.36.1, 1.35.2, 1.34.2, or 1.33.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.