-
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 missing oms_agent[0].oms_agent_identity[0] #21305
Comments
Some updates. I have tested and this issue definitely related to AAD enabled clusters, I have deployed a cluster in a Sandbox without integration and worked fine. Also this issue does not happening on 3.51.0, maybe because of the API version change to |
I am seeing the same issue with 3.52.0 |
Issue still present on v3.67.0 |
Same issue on v3.69.0 |
When I tried removing/enabling the monitoring addon via the Azure CLI, (i.e. outside of Terraform) I noticed that the config had a null identity when AAD auth is enabled |
Same issue here, when "msi_auth_for_monitoring_enabled" is true, the "oms_agent_identity" becomes empty |
Same issue |
For Managed Identity enabled clusters, the identity object is expected to be null. To enable omsagent there will also be a need to have Data Collection Rules(DCRs) and Data Collection Rule Association (DCRAs). Please follow the guide here for onboarding using terraform: https://github.com/microsoft/Docker-Provider/tree/ci_prod/scripts/onboarding/aks/onboarding-msi-terraform |
Is there an existing issue for this?
Community Note
Terraform Version
1.4.2
AzureRM Provider Version
3.49.0
Affected Resource(s)/Data Source(s)
azurerm_kubernetes_cluster
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
Statefile should have the oms_agent_identity populated.
Actual Behaviour
Statefile does not have the oms_agent_identity stored.
Steps to Reproduce
Create a cluster with OMS Agent enabled.
I could reproduce this on 3.39.0 as well.
On 3.31.0 this was working fine.
Important Factoids
No response
References
This issue looks really similar to the one, when the kube_config was not populated for an AAD enabled cluster.
#18139
#18142
I have not tested without AAD enabled as this is a constrain in my environment.
The text was updated successfully, but these errors were encountered: