Upgrades have been made to the service which powers Kubernetes & Container Orchestration (including Clusters and Stacks) in the Nectar Cloud. This service is also known by the name Magnum.
Significant Changes
New: Support Kubernetes v1.25.9
New: The default StorageClass is now created in a new cluster
Removed: PodSecurityPolicy has been removed. New clusters will no longer have PodSecurityPolicy by default. This is because Kubernetes has removed this in v1.25.
Upgrade: Containerd is now the only available runtime for v1.25. This because Kubernetes removed Dockershim in v1.24. v1.23 is the changeover version from docker to containerd, where it supports both runtimes. See below for more details moving from docker to containerd.
Deprecated: Kubernetes v1.21 templates are now deprecated. They have been removed from public view and we will gradually phase out support.
Caution required
As there are major changes in upstream Kubernetes, please exercise caution when moving from v1.21 and older. You can use Magnum to easily create new clusters with varying Kubernetes versions and runtimes to test your code on. One strategy is to test with the following sequence:
Jake Yip
Upgrades have been made to the service which powers Kubernetes & Container Orchestration (including Clusters and Stacks) in the Nectar Cloud. This service is also known by the name Magnum.
Significant Changes
New: Support Kubernetes v1.25.9
New: The default StorageClass is now created in a new cluster
Removed: PodSecurityPolicy has been removed. New clusters will no longer have PodSecurityPolicy by default. This is because Kubernetes has removed this in v1.25.
Upgrade: Containerd is now the only available runtime for v1.25. This because Kubernetes removed Dockershim in v1.24. v1.23 is the changeover version from docker to containerd, where it supports both runtimes. See below for more details moving from docker to containerd.
Deprecated: Kubernetes v1.21 templates are now deprecated. They have been removed from public view and we will gradually phase out support.
Caution required
As there are major changes in upstream Kubernetes, please exercise caution when moving from v1.21 and older. You can use Magnum to easily create new clusters with varying Kubernetes versions and runtimes to test your code on. One strategy is to test with the following sequence:
v1.21.1 (docker) -> v1.23.8 (docker) -> v1.23.8 (containerd) -> v1.25.9 (containerd)
This can help identify which components of Kubernetes require an upgrade.
Container Runtime
Magnum templates supports the following container runtime
Kubernetes version in template
Container runtime
v1.17.11
docker
v1.21.1
docker
v1.23.8
docker, containerd
v1.25.9
containerd
Server version
You can check what version your cluster is using by using kubectl version
Server Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.8"
Container Runtime version
You can check what container runtime your cluster is using by
`kubectl cluster-info-dump`
For containerd, it will look like this
$ kubectl cluster-info dump | grep containerRuntime
"containerRuntimeVersion": "containerd://1.6.6",
"containerRuntimeVersion": "containerd://1.6.6",
For docker, it will look like this
$ kubectl cluster-info dump | grep containerRuntime
"containerRuntimeVersion": "docker://20.10.11",
"containerRuntimeVersion": "docker://20.10.11",
If you require assistance please submit a request via the Nectar Support site.