-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
azurerm_kubernetes_cluster: add support for enableNodePublicIP #4581
Comments
I could tackle this! Currently I've used following approach when working with public IPs and, for example, AKS ingress: resource "azurerm_public_ip" "nginx_ingress" {
name = "nginx-ingress-pip"
location = azurerm_kubernetes_cluster.aks.location
resource_group_name = azurerm_kubernetes_cluster.aks.node_resource_group
allocation_method = "Static"
domain_name_label = "cool-domain-k8s"
} and personally I believe that enabling public IP simply in agent pool profile would result to a slightly cleaner approach. |
FWIW this property is captured under issue #4001 which should exist as an agent pool profile property. Also for awareness this capability is still in preview so that's a good callout if it does get brought in. |
hey @iameli @topikettunen has added support for this in #4613 which has merged and will ship as a part of 1.37 - as such I'm going to close this issue for the moment. Taking a look through it appears the documentation for this field is missing, but I've got a fix for this locally which I'll push with a related PR later today. Thanks! |
This has been released in version 1.37.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example: provider "azurerm" {
version = "~> 1.37.0"
}
# ... other configuration ... |
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks! |
Community Note
Description
Azure has added support for an
enableNodePublicIP
field in the AgentPoolProfile schema. Would be nice to be able to make use of it from Terraform.New or Affected Resource(s)
Potential Terraform Configuration
I'm going to need something like this within the next couple of months, so I'll implement it then unless someone else beats me to it.
The text was updated successfully, but these errors were encountered: