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 setting GPU MIG instance profiles on AKS node pools #23880

Closed
1 task done
somehowadev opened this issue Nov 13, 2023 · 2 comments · Fixed by #23887
Closed
1 task done

Support setting GPU MIG instance profiles on AKS node pools #23880

somehowadev opened this issue Nov 13, 2023 · 2 comments · Fixed by #23887

Comments

@somehowadev
Copy link

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 "+1" or "me too" comments, 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

It is possible to create GPU node pools in AKS with MIG instance profiles.

It would be ideal if azurerm_kubernetes_cluster_node_pool supported this new property.

If the property is changed, the resource would need to be recreated.

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

azurerm_kubernetes_cluster_node_pool

Potential Terraform Configuration

resource "azurerm_kubernetes_cluster_node_pool" "example" {
  name                  = "internal"
  kubernetes_cluster_id = azurerm_kubernetes_cluster.example.id
  vm_size               = "Standard_NC96ads_A100_v4"
  node_count            = 1

  mig_strategy          = "MIG7g"

  tags = {
    Environment = "Production"
  }
}

References

@rcskosir
Copy link
Contributor

Thank you for taking the time to open this issue. Please subscribe to PR #23887 created by @ms-henglu for this issue.

Copy link

github-actions bot commented May 1, 2024

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 1, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.