We are excited to announce the availability of Kubernetes v1.13.2 for your clusters that are running in IBM Cloud Kubernetes Service.
We are excited to announce the availability of Kubernetes v1.13.2 for your clusters that are running in IBM Cloud Kubernetes Service. With the Kubernetes service, you can easily upgrade your clusters without the need for deep Kubernetes knowledge. When you deploy new clusters, the default Kubernetes version remains 1.10; you can also choose to immediately deploy version 1.13. Learn more about deploying clusters here.
What does containerd mean for my clusters?
For clusters that run Kubernetes version 1.11 or later, containerd replaces Docker as the container runtime for Kubernetes to enhance performance. If your pods rely on Docker as the Kubernetes container runtime, you must update them to handle containerd as the container runtime. For more information and update actions, see IBM Cloud Kubernetes Service Supports containerd.
Kubernetes v1.13
In addition to all the great Kubernetes features provided in this release, the IBM Cloud Kubernetes Service v1.13 update also includes:
-
Ability to select CoreDNS (default for new clusters) or KubeDNS as cluster DNS provider.
-
Multiple Corefiles can now be used to configure CoreDNS.
See the IBM Cloud Kubernetes Service version 1.13 changelog for details.
Kubernetes support and updates
IBM Cloud Kubernetes Service now supports the latest four versions of Kubernetes: 1.10, 1.11, 1.12, and 1.13. Clusters that are running Kubernetes versions 1.9 and earlier are unsupported. Clusters running 1.10 will soon be deprecated, with end of support tentatively scheduled for March 29.
It is important to note that clusters that run unsupported Kubernetes versions cannot receive security updates or support until they are updated to a supported version. Review the potential impact of each Kubernetes version update, and update your clusters immediately to version 1.11 or later.
For general questions, engage our team via Slack by registering here and join the discussion in the #general channel on our public IBM Cloud Kubernetes Service Slack.