Share via

Error when upgrading node pool: Kind and SKU Basic do not match

Thomas Ervik 1 Reputation point
2024-06-21T11:39:57.9966667+00:00

I am encountering an error when trying to upgrade a node pool in Germany West Central. The error message says:

(BadRequest) Kind  and SKU Basic do not match, please make them match or not set Kind
Code: BadRequest
Message: Kind  and SKU Basic do not match, please make them match or not set Kind

I have successfully updated several other node pools in other clusters (in other regions) with the same setup without any errors. Here is some additional information:

  • Kubernetes version: 1.27.7
  • OS image: AKSUbuntu-2204containerd-202405.20.0
  • Update image: AKSUbuntu-2204containerd-202405.27.0

Can anyone help me understand the issue and how to fix it?

Command used to upgrade node image:
az aks nodepool upgrade --resource-group rg-aks --cluster-name aks-abc --name apps --node-image-only

Azure Kubernetes Service (AKS)
Azure Kubernetes Service (AKS)
An Azure service that provides serverless Kubernetes, an integrated continuous integration and continuous delivery experience, and enterprise-grade security and governance.
1,956 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. vipullag-MSFT 25,611 Reputation points
    2024-06-24T03:54:38.0333333+00:00

    Hello Thomas Ervik

    Welcome to Microsoft Q&A Platform, thanks for posting your query here.

    As the upgrade was successful in other regions, it's possible that the issue is specific to the node pool in Germany West Central.

    The error message you are seeing indicates that the SKU of the node pool is set to "Basic" while the kind of the node pool is set to something else.

    Try these troubleshooting steps to resolve this issue, you can either set the SKU to match the kind or remove the kind setting altogether.

    If the issue persists, you can try removing the kind setting from the node pool and then running the upgrade command again.

    After removing the kind setting, you can run the upgrade command again.

    Hope this helps.

    0 comments