v1.20.15

On Premises add-on module release 1.20.15

Welcome to the latest release of on-premises module of Kubernetes Fury Distribution maintained by team
SIGHUP.

⚠️ This minor relases consolidates the repository adding enhanced capabilities like the addition of the containerd ansible role.
Docker installation was also removed from kube-node-common ansible role and moved to a dedicated docker ansible role.

Package Versions 🚢

Package	Supported Version	Previous Version
vmware-cm	1.2.1	Updated
vmware-csi	2.1.0	Updated
etcd	3.4.7	No update
haproxy	2.2	No update
containerd	1.5.8	New Package
docker	19.X	Updated
kube-node-common	1.20.15	Updated
kube-control-plane	1.20.15	Updated
kube-worker	1.20.15	Updated

Removed packages 🚮

• dex package has been removed. A new Kubernetes Fury add-on module will contain the dex package.
• gangway package has been removed. A new Kubernetes Fury add-on module will contain the gangway package.
• furyagent package has been removed. A newer updated version can be found in the Kubernetes Fury Furyagent module.

New package: Welcome containerd ansible role! 📕

This release adds the containerd ansible role to prepare the path for the docker removal in Kubernetes version 1.24.

Update Guide 🦮

In this guide, we will try to summarize the update process for these release.

NOTE: Each on-premises environment can be different, always double-check before updating components.

dex

To update dex package, please run the following command:

kustomize build <your-project-path-including-dex-as-base> | kubectl apply -f -

vsphere-cm

The vSphere controller manager update can be executed before upgrading the cluster version to v1.20.x.
The current versions is compatible with Kubernetes 1.20.x and it's standard skew versions.

Due to some changes on the manifests, you need to change the patch on the secrets used by the vsphere controller manager:

• rename Secret vsphere-credentials to vsphere-cloud-secret
• rename Secret cloud-config to vsphere-cloud-config

Delete the daemonset vsphere-cloud-controller-manager (due to immutable fields):

kubectl delete ds vsphere-cloud-controller-manager -n kube-system

Once everything is done, please run the following command:

kustomize build <your-project-path-including-vmware-cm-as-base> | kubectl apply -f -

vsphere-csi

The vSphere CSI driver update is a little bit more complicated. In this version the CSI driver DaemonSet and Deployment
are moved to a new dedicated namespace vmware-system-csi. To address this we need to first delete the current CSI driver from the cluster:

kubectl delete -f katalog/vsphere-csi/vsphere-csi-controller-deployment.yaml
kubectl delete -f katalog/vsphere-csi/vsphere-csi-node-ds.yaml
kubectl delete -f katalog/vsphere-csi/vsphere-csi-controller-rbac.yaml
kubectl delete -f katalog/vsphere-csi/csi-vsphere-secret.yml

Now, download the new katalog package in your project, change the patch applied to the vsphere-config-secret to use the new namespace
and apply the new version:

kustomize build <your-project-path-including-vmware-csi-as-base> | kubectl apply -f -