...

To upgrade major versions you will need to follow the https://stfc.atlassian.net/wiki/spaces/CLOUDKB/pages/285704256/Cluster+API+Upgrade#Upgrade-Clusterctl-and-CAPI-components section first then https://stfc.atlassian.net/wiki/spaces/CLOUDKB/pages/285704256/Cluster+API+Upgrade#UpgradingUpgrade#Kubernetes-KubernetesImage-Majorand-Version-Upgrades for each hop.

Overview

This process assumes the administrator is doing a full upgrade of all components. These can be upgraded independently with the caveat that the Infrastructure layer supports the version of Kubernetes planned: https://cluster-api.sigs.k8s.io/reference/versions

...

• Validate that the upgrade is valid and apply the command provided by clusterctl

Kubernetes Image and Version Upgrades

Without minor version upgrade

...

You’ll need to upgrade VM images and Kubernetes version to the latest patch version available

...

before doing any major upgrades:

I.e. if you’re on 1.100.12 upgrade to the latest 1.100.x, this ensures any bug-fixes are applied which could prevent later upgrades.

For major and minor

...

upgrades

...

:

• Lookup the latest image build for Kubernetes, this can be found in images section of the web interface

• Edit the kubernetesVersion in user-values.yaml

...

• to

...

• match the image name

• Edit the machineImage in user-values.yaml

...

• to

...

• use the latest patch release

helm upgrade <cluster_name> capi/openstack-cluster -f values.yaml -f clouds.yaml -f user-values.yaml -f flavors.yaml -n clusters

• Wait for the rollout of new infra to complete

  • The rollout can be monitored with kubectl get kcp -A and kubectl get md -A

  • Machine details can be found in kubectl get machines -A and kubectl get openstackmachines -A

With minor version upgrade

• Upgrade to the Repeat for each major upgrade step

  • You can only do a single major upgrade at a time, e.g. 1.100.12 to 1.101.4, then 1.102.6

Troubleshooting

On the management cluster

...