[BUG]Output of updating AKS cluster to premium tier has Discrepancies in the portal and CLI.

[anilkumar1619]

Output of updating AKS cluster to premium tier has Discrepancies in the portal and CLI.

Issue:

I tried to update one of my AKS clusters tiers to Premium from Standard which is running on 1.30.4 and the operation went through successfully but by default it changed the support plan to "AKSLongTermSupport" and I believe this is expected but I don't see this in documentation or as a note so that customer is aware while updating the tier.

As I don't want the cluster with "AKSLongTermSupport", I tried to reverted the changes and after sometime, I updated the cluster again to premium tier from standard by mentioning "--k8s-support-plan KubernetesOfficial" and expected this too fail but this worked and cluster tier is updated to Premium without any issues and the k8s-support-plan was set to Kubernetesofficial only.

I expected that everything is fine but that is when I noticed a descrepancy in the output where the json view in the portal on AKS cluster is showing "AKSLongTermSupport" whereas the CLI output of az aks show -g -n | grep -i supportplan showas "kubernetesofficial" for the same cluster and the k8s-version in the portal shows 1.30.4 LTS whereas the CLI output shows just 1.30.4.

This is all for the cluster running with 1.30.4.

This time I tried to update the cluster running with 1.29.9 to premium from the portal and the update went through successfully but found couple of issues.
As 1.29.9 is not a LTS version, it is expected that the support plan by default should be "Kubernetesofficial" unlike above and it was correct even after updating to premium.

Support plan stayed as "kubernetesofficial" whereas the version in the portal showed as 1.29.9 LTS whereas in the CLI it shows as 1.29.9.

===========

Ask on this Github issue:

Is it expected that the support plan changes by default to "AKSLongTermSupport" if the cluster version is eligible for LTS. If yes, can we update the document as a note so that customers are aware of it.
Can we explicitly mention support plan to "kubernetesofficial" for the clusters even though they are supported for LTS. (I already did this, and it was successful).
If yes, could you update the document as well.
Why do we have discrepancies with outputs in CLI and portal.
Why is portal showing 1.29.9 LTS for a non-LTS version and why we have discrepancies in portal and CLI output for it too. Below error clearly says that 1.29.9 is a non-LTS version.

Submitted MicrosoftDocs/azure-aks-docs#115 github issue for document update.

Kindly assist.

[chandraneel]

Thanks for the report, taking a look. Will update soon.

[keshavprasad123]

Thank you for reporting the issue. We appreciate your feedback and want to inform you that the Premium SKU previously only supported the LTS support plan. However, with recent changes, KubernetesOfficial is now also supported for the Premium SKU. We are planning to update the portal behavior to reflect this change and add support for KubernetesOfficial in January 2025.