IBM Cloud Docs
1.24 version information and update actions

1.24 version information and update actions

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

Review information about version 1.24 of IBM Cloud® Kubernetes Service, released 09 June 2022.

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.24 certification for IBM Cloud Kubernetes Service
Kubernetes version 1.24 certification badge

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

Release timeline

The following table includes the expected release timeline for version 1.24 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.24
Version Supported? Release date Unsupported date
1.24 Yes 09 Jun 2022 14 December 2023

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.24. For a complete list of changes, review the community Kubernetes change log and IBM version change log for version 1.24. You can also review the Kubernetes helpful warnings.

Update before master

Pod security policies are scheduled for removal in Kubernetes version 1.25. See the Kubernetes Deprecated API migration guide for more information. Customers have the option to replace Pod Security Policies with Pod security admission or a third party admission webhook. IBM Cloud Kubernetes Service will make a beta version of Pod Security available in version 1.24 to aid in the migration, but this support is not yet available.

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

Changes to make after you update the master to Kubernetes 1.24
Type Description
IBM Cloud Block Storage driver and plug-in installation The IBM Cloud Block Storage driver and plug-in component is now installed on clusters running classic infrastructure. If you installed the IBM Cloud Block Storage driver and plug-in via the Helm chart, you must uninstall the Helm chart before continuing the master update. Note that your existing persistent volume claims (PVCs) will continue to work after the Helm chart is uninstalled, but you are not able to provision new PVCs until the master update is completed. To uninstall the Helm chart, see Removing the Block Storage Helm chart.
Updated default container network sysctls New containers running on the pod network will have the following sysctl tuning applied by default: net.ipv4.tcp_keepalive_intvl=15, net.ipv4.tcp_keepalive_probes=6 and net.ipv4.tcp_keepalive_time=40. If your apps rely on the previous defaults, you must update your app deployment to customize the sysctl settings. See Optimizing network keepalive sysctl settings for details.

Removing the Block Storage Helm chart

  1. Add the iks-charts repo and update it.
    helm repo add iks-charts https://icr.io/helm/iks-charts && helm repo update
    
  2. List the Helm deployments in your cluster and make a note of the Block Storage for Classic plug-in deployment in the kube-system namespace.
    helm ls -A
    
  3. Delete the plug-in from your cluster by using the helm delete command.
    helm delete RELEASE -n kube-system
    
  4. List pods in the kube-system namespace to verify the plug-in pods have been removed.
    kubectl get pods -n kube-system | grep block
    

Update after master

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

Changes to make after you update the master to Kubernetes 1.24
Type Description
Unsupported: kubectl expose removes --container-port and --generator options The kubectl expose command no longer supports the deprecated --container-port and --generator options. If your scripts rely on these options, update them.
Unsupported: kubectl run removes several options The kubectl run command no longer supports the deprecated --serviceaccount, --hostport, --requests and --limits options. If your scripts rely on these options, update them.