1.27 version information and update actions

Review information about version 1.27 of IBM Cloud® Kubernetes Service.

This version is no longer supported. Update your cluster to a supported version as soon as possible.

Looking for general information on updating IBM Cloud® Kubernetes Service clusters, or information on a different version? See Kubernetes version information and update actions.

Kubernetes version 1.27 certification badge

IBM Cloud Kubernetes Service is a Certified Kubernetes product for version 1.27 under the CNCF Kubernetes Software Conformance Certification program. Kubernetes® is a registered trademark of The Linux Foundation in the United States and other countries, and is used pursuant to a license from The Linux Foundation.

For more information about Kubernetes project version 1.27, see the Kubernetes change log.

Release timeline

The following table includes the expected release timeline for version 1.27 of IBM Cloud® Kubernetes Service. You can use this information for planning purposes, such as to estimate the general time that the version might become unsupported.

Dates that are marked with a dagger (†) are tentative and subject to change.

Release timeline for IBM Cloud Kubernetes Service version 1.27
Version	Supported?	Release date	Unsupported date
1.27	Yes	24 May 2023	18 September 2024 `†`

Preparing to update

This information summarizes updates that are likely to have and impact on deployed apps when you update a cluster to version 1.27. For a complete list of changes, review the community Kubernetes change log and IBM version change log for version 1.27. You can also review the Kubernetes helpful warnings.

Update before master

The following table shows the actions that you must take before you update the Kubernetes master.

Changes to make before you update the master to Kubernetes 1.27
Type	Description
Unsupported: Beta version of the `CSIStorageCapacity` API	Migrate manifests and API clients to use the `storage.k8s.io/v1` API version, available since Kubernetes version 1.24. For more information, see Deprecated API Migration Guide - v1.27.
Unsupported: Pod `seccomp.security.alpha.kubernetes.io/pod` and `container.seccomp.security.alpha.kubernetes.io` annotations	Kubernetes no longer supports the pod `seccomp.security.alpha.kubernetes.io/pod` and `container.seccomp.security.alpha.kubernetes.io` annotations. These annotations have been deprecated since Kubernetes version 1.19 and has been replaced by the `securityContext.seccompProfile` field for pods and containers. If your pods rely on these unsupported annotations, update them to use the `securityContext.seccompProfile` field instead. For more information, see Create Pod that uses the container runtime default `seccomp` profile.
`k8s.gcr.io` redirect to `registry.k8s.io`	Kubernetes version 1.27 release artifacts are not published to the `k8s.gcr.io` registry. Furthermore, `k8s.gcr.io` registry traffic are redirected to `registry.k8s.io`. For more information, see k8s.gcr.io Redirect to registry.k8s.io - What You Need to Know. Note that IBM Cloud Kubernetes Service has already handled this migration action for all resources provided by IBM.
`kubelet` legacy iptables rules	`kubelet` no longer creates certain legacy iptables rules by default. It is possible that this will cause problems with some third-party components that improperly depended on those rules. For more information, see Kubernetes’s IPTables Chains Are Not API.