-
Notifications
You must be signed in to change notification settings - Fork 4.5k
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 - api_server_authorized_ip_ranges does not work #21411
Comments
Thanks for raising this issue @manoj7shekhawat. As an aside this property is deprecated and you should switch over to using Thanks! |
Thank you @stephybun for closing this issue. It would be nicer if we could have got a terraform warning for the deprecation for the property. |
@manoj7shekhawat there is a deprecation message set for the property in the provider which should be output when running a Terraform. |
@stephybun thanks for your inputs yes you are right it's swallowed but NOT by Azure DevOps it's actually by other deprecation warnings and we end up with this: We have to work quickly to remove all deprecation warnings. |
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. |
Is there an existing issue for this?
Community Note
Terraform Version
1.4.4
AzureRM Provider Version
3.49.0
Affected Resource(s)/Data Source(s)
azurerm_kubernetes_cluster
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
After terraform apply, the "Specify IP ranges" under "Networking" in Azure Kubernetes Service should be added to the existing list of CIDR.
Actual Behaviour
The "Specify IP ranges" under "Networking" in Azure Kubernetes Service is NOT updated. It still contains the old list of CIDR.
Steps to Reproduce
terraform apply
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered: