AWS Provider / Rollout updates not working

[gustavosr98]

Just updating the version in the spec does not result in an update of the k8s version

Available versions

# ubuntu@ip-172-31-30-109:~/cluster-api-k8s/templates/aws$ snap info k8s | grep 1.32
tracking:     1.32-classic/stable
  1.32-classic/stable:    v1.32.3 2025-05-05 (3315) 142MB classic
  1.32-classic/candidate: v1.32.3 2025-04-23 (3315) 142MB classic
  1.32-classic/beta:      v1.32.4 2025-05-05 (3406) 143MB classic
  1.32-classic/edge:      v1.32.4 2025-05-05 (3422) 143MB classic
  1.32-moonray/stable:    v1.32.3 2025-05-05 (3314) 142MB classic
  1.32-moonray/candidate: v1.32.3 2025-04-23 (3314) 142MB classic
  1.32-moonray/beta:      v1.32.4 2025-05-05 (3407) 143MB classic
  1.32-moonray/edge:      v1.32.4 2025-05-05 (3421) 143MB classic
installed:                v1.32.3            (3315) 142MB classic

I do see a rollout, but the result is three new machines with the same old version 1.32.3 instead of 1.32.4

# ubuntu@ip-172-31-30-109:~/cluster-api-k8s/templates/aws$ KUBECONFIG=./cluster-x-kubeconfig kubectl get node
NAME                          STATUS   ROLES                  AGE     VERSION
ip-10-0-0-179.ec2.internal    Ready    worker                 27m     v1.32.3
ip-10-0-16-117.ec2.internal   Ready    control-plane,worker   5m49s   v1.32.3
ip-10-0-35-174.ec2.internal   Ready    control-plane,worker   9m8s    v1.32.3
ip-10-0-6-168.ec2.internal    Ready    control-plane,worker   12m     v1.32.3
ip-10-0-8-10.ec2.internal     Ready    worker                 27m     v1.32.3

---

Document: capi/howto/rollout-upgrades.md

[gustavosr98]

Giving it a try by updating version + channel

apiVersion: controlplane.cluster.x-k8s.io/v1beta2
kind: CK8sControlPlane
spec:
[..]
  spec:
    channel: 1.32-classic/edge
[..]
  version: v1.32.4

But got to the same result

[HomayoonAlimohammadi]

Thanks for bringing this up @gustavosr98!
I can see how this is confusing, and we need to either document it well enough or refactor the implementation a bit.
But here's the story:
Patch versions are handled by the snap that you're installing.
So if you've specified version: v1.32.X, the latest patch version offered by the 1.32-classic/stable snap is going to be installed, regardless of X.
For the same reason, changing the patch version won't result in different snaps getting installed (since only major and minor versions are considered to pick the correct snap channel, e.g. 1.32-classic/stable).
In order to perform a rollout upgrade, we need to at least bump a minor version. So changing the version from v1.31.X -> v1.32.Y should result in an upgrade.

[HomayoonAlimohammadi]

So we can go with the following cluster.yaml:

apiVersion: controlplane.cluster.x-k8s.io/v1beta2
kind: CK8sControlPlane
spec:
[..]
  version: v1.31.0

Which will install the 1.31-classic/stable snap (with whatever patch version that it comes with), and later change it to

apiVersion: controlplane.cluster.x-k8s.io/v1beta2
kind: CK8sControlPlane
spec:
[..]
  version: v1.32.0

Edit: Note that there are two version fields for the CK8sControlPlane object and you need to play with the outer one.
This ambiguity needs to be addressed and clarified in a future task.
Inner version:

kind: CK8sControlPlane
spec:
  [..]
  spec:
    [..]
    version: v1.31.0

Outer version:

kind: CK8sControlPlane
spec:
  [..]
  version: v1.31.0

[HomayoonAlimohammadi]

To be clarified and addressed in KU-3442.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.