IBM Cloud Docs
1.26 version information and update actions

1.26 version information and update actions

Review information about version 1.26 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.

This badge indicates Kubernetes version 1.26 certification for IBM Cloud Kubernetes Service
Kubernetes version 1.26 certification badge

IBM Cloud Kubernetes Service is a Certified Kubernetes product for version 1.26 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.26, see the Kubernetes change log

Release timeline

The following table includes the expected release timeline for version 1.26 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.26
Version Supported? Release date Unsupported date
1.26 Yes 01 February 2023 31 May 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.26. For a complete list of changes, review the community Kubernetes change log and IBM version change log for version 1.26. 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. Initial 1.26 version information and update actions

When you upgrade your cluster to version 1.26, a BGP password is automatically configured for Calico. This results in a several second disruption to pod networking while the BGP password configuration is applied.

Changes to make before you update the master to Kubernetes 1.26
Type Description
Unsupported: Beta version of the FlowSchema and PriorityLevelConfiguration API Migrate manifests and API clients to use the flowcontrol.apiserver.k8s.io/v1beta2 API version, available since Kubernetes version 1.23. For more information, see Deprecated API Migration Guide - v1.26.
Unsupported: Beta version of the HorizontalPodAutoscaler API Migrate manifests and API clients to use the autoscaling/v2 API version, available since Kubernetes version 1.23. For more information, see Deprecated API Migration Guide - v1.26.
Unsupported: Storage class volume.beta.kubernetes.io/storage-class beta resource annotation Migrate manifests and API clients to use the spec.storageClassName field on the PersistentVolumeClaim and PersistentVolume resources instead.
Unsupported: Select Kubernetes API server metrics replaced The following Kubernetes API service metrics were replaced: etcd_db_total_size_in_bytes is replaced by apiserver_storage_db_total_size_in_bytes, job_sync_total is replaced by job_syncs_total, job_finished_total is replaced by jobs_finished_total, and cronjob_job_creation_skew_duration_seconds is replaced by job_creation_skew_duration_seconds. If you rely on these replaced metrics, update accordingly.

Update after master

Changes to make after you update the master to Kubernetes 1.26
Type Description
Unsupported: localhost NodePort services To further reduce security risks related to CVE-2020-8558, localhost access to NodePort services has been disabled. If you apps rely on this behavior, update them to the node private IP address instead.
Unsupported: Legacy kubectl options relating to logging The following legacy kubectl logging options have been removed: --log-dir, --log-file, --log-flush-frequency, --logtostderr, --alsologtostderr, --one-output, --stderrthreshold, --log-file-max-size, --skip-log-headers, --add-dir-header, --skip-header, and --log-backtrace-at. If your scripts rely on these flags, update them accordingly. For more information, see Removal of legacy command line arguments relating to logging.