aksv2 - for imported clusters, when performing Edits, UI thinks k8s version has been updated

[prabalsharma]

For imported clusters, when performing Edits from Rancher, UI thinks k8s version has been updated even when thats not the case.

1. Import AKS cluster
2. Once Active, click Edit
3. Go to NPs. You will see the following even when k8s version has not been changed

This goes away once k8s version of CP is actually upgraded from Rancher.

(This was a Docker install of v2.6-e22c6bb23ee7e65f04e953afb7a449532cb44db0-head)

Feel free to change the milestone to 2.6.x

[claudioser]

similar findings when "mistakenly" upgrading from Kubernetes v1.19.11 to 1.21.11. Receive msg that upgrade is not allowed. See screenshot.

When trying to edit cluster again and rectifying it to a upgradable version, unable to do so as it thinks it is already upgraded..

[gaktive]

As noted by @vincent99, this is adopted behaviour from kubectl, so the UI is given the same info as you'd see outside of Rancher. Working as designed unless you can show a discrepancy from kubectl.

[vincent99]

@gaktive I don't think your comment is on the right issue? I don't know what the cause of this one is but it has nothing to do with kubectl.

[gaktive]

@vincent99 I'll put this back in our pile to look at then. I need to then find out which comment that was meant for...

[yonasberhe23]

seems like there are no e2e/unit tests attached to the fix (I'm guessing it's because we don't have a way to create clusters in a cloud provider - please advise @mantis-toboggan-md) so we'll need to manually test this. moving to To Test

[yonasberhe23]

Tested in:

• v2.9-3c4ccdc5bc9fde3510089153b5ad58fdbe604880-head
• master 84975df

No longer seeing the message when k8s version has not been changed on an imported cluster - only appears when version changed

Screen.Recording.2024-07-11.at.11.02.35.AM.mov

[gaktive]

Fixing milestone since this was still in the .x backlog.