Skip to content


Kubernetes upgrades

Check the versions skew policy

  1. Scale down admiralty deployments and delete all virtual nodes - those prevent the upgrades
  2. Make sure the etcd size fits the standard limit (2GB).

nerdctl run --rm --network host -v /etc/kubernetes/pki/etcd:/etc/kubernetes/pki/etcd:ro --env ETCDCTL_API=3 etcdctl --endpoints= --cacert=/etc/kubernetes/pki/etcd/ca.crt --cert=/etc/kubernetes/pki/etcd/healthcheck-client.crt --key=/etc/kubernetes/pki/etcd/healthcheck-client.key --write-out=table endpoint status

If it doesn't, perform compaction.

  1. Follow the upgrade guide for master.
  2. During the upgrade it's better to pre-pull the new images with kubeadm config images pull
  3. From backup of manifests put back the CiLogon settings to the current apiserver manifest in /etc/kubernetes/manifests,
  4. Bring back all custom changes to controller-manager and etcd manifests in /etc/kubernetes/manifests.
  5. Do the last step in the upgrade manual to restart the control place again.

-- Breathe out! The master upgrade is done. --

  1. Do rolling upgrade of compute nodes using ansible upgrade playbook.
  2. Upgrade the kubernetes version in the portal dependencies libraries