Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for Azure D series 6-th generation VMs in AKS #28252

Open
1 task done
stremovsky opened this issue Dec 11, 2024 · 5 comments
Open
1 task done

Support for Azure D series 6-th generation VMs in AKS #28252

stremovsky opened this issue Dec 11, 2024 · 5 comments

Comments

@stremovsky
Copy link

stremovsky commented Dec 11, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave comments along the lines of "+1", "me too" or "any updates", they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment and review the contribution guide to help.

Description

Hello

I’m running into an issue deploying an AKS cluster with a new generation of virtual machines available in Azure. I am using the Standard_D8ads_v6 VM size. The same setup works fine with Standard_D8ads_v5.

Here’s the error I’m getting:

(BadRequest) Code="BadRequest" Message="The selected VM size 'Standard_D8ads_v6' cannot boot 
Hypervisor Generation '1'. If this was a Create operation please check that the Hypervisor Generation of 
the Image matches the Hypervisor Generation of the selected VM Size. If this was an Update operation 
please select a Hypervisor Generation '1' VM Size. For more information, see https://aka.ms/azuregen2vm"

I was able to create the node pool using the Azure CLI with this command:

az aks nodepool add --cluster-name cluster-eus1 --resource-group cluster-eus1 \
  --name test --node-osdisk-type Ephemeral --node-vm-size Standard_D8ads_v6 \
  --node-count 1 --os-type Windows --os-sku Windows2022 --aks-custom-headers UseWindowsGen2VM=true

But I need a Terraform-based solution to achieve the same result.

Thanks!
Yuli

New or Affected Resource(s)/Data Source(s)

azurerm_kubernetes_cluster_node_pool

Potential Terraform Configuration

resource "azurerm_kubernetes_cluster_node_pool" "windows" {
  name                  = "wpool"
  kubernetes_cluster_id = azurerm_kubernetes_cluster.example.id
  vm_size               = "Standard_D8ads_v6"
  os_type               = "Windows"
  os_sku                = "Windows2022"
  os_disk_type          = "Ephemeral"
  orchestrator_version  = "1.31"
  node_labels = {
    "purpose" = "windows-workloads"
  }

  enable_auto_scaling = true
  min_count           = 1
  max_count           = 5
}

References

No response

@stremovsky stremovsky changed the title Support for Azure D series 6-th generation Support for Azure D series 6-th generation VMs Dec 11, 2024
@stremovsky stremovsky changed the title Support for Azure D series 6-th generation VMs Support for Azure D series 6-th generation VMs in AKS Dec 11, 2024
@Transformer-cloud
Copy link

Hi
I also facing the same Issue with my customers.
@hc-github-team-tf-azure
Please help

@dor-trabelsi
Copy link

Hey, Facing the same issue.

@rancohen-pictime
Copy link

+1

@golovasheveo
Copy link

The same issue -aks-custom-headers

@aalmog999
Copy link

Hi Guys,
i also getting this issue when trying to implement this type of vm's from terraform and portal...
Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants