Open AhrazA opened 9 months ago
I observed the same thing. In addition, tf installs the relayserver on AKS which was not supposed to be the case according to the documentation. I guessed the cluster type was not being addressed.
@AhrazA @jmasengeshomsft I managed use azurerm_kubernetes_cluster_extension for ml using this code:
resource "azurerm_kubernetes_cluster_extension" "aml" {
name = "aml"
cluster_id = azurerm_kubernetes_cluster.aks.id
extension_type = "microsoft.azureml.kubernetes"
configuration_settings = {
"enableTraining" = "false"
"enableInference" = "true"
"inferenceRouterServiceType" = "LoadBalancer"
"internalLoadBalancerProvider" = "azure"
"allowInsecureConnections" = "true"
"InferenceRouterHA" = "false"
"cluster_name" = azurerm_kubernetes_cluster.aks.id
"domain" = "${azurerm_resource_group.aml.location}.cloudapp.azure.com"
"location" = azurerm_resource_group.aml.location
"jobSchedulerLocation" = azurerm_resource_group.aml.location
"cluster_name_friendly" = azurerm_kubernetes_cluster.aks.name
"servicebus.enabled" = "false"
"relayserver.enabled" = "false"
"nginxIngress.enabled" = "true"
"clusterId" = azurerm_kubernetes_cluster.aks.id
"prometheus.prometheusSpec.externalLabels.cluster_name" = azurerm_kubernetes_cluster.aks.id
}
}
Is there an existing issue for this?
Community Note
Terraform Version
1.3.3
AzureRM Provider Version
3.80.0
Affected Resource(s)/Data Source(s)
azurerm_kubernetes_cluster_extension
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
The extension "Microsoft.AzureML.Kubernetes" should be successfully applied to the managed AKS cluster.
Actual Behaviour
The ML extension is deployed, but fails to validate the SSL settings.
The same configuration works via the CLI:
Steps to Reproduce
azurerm_kubernetes_cluster_extension
with extension_typeMicrosoft.AzureML.Kubernetes
and with thesslSecret
optionImportant Factoids
No response
References
It seems very similar to this issue: https://github.com/hashicorp/terraform-provider-azurerm/issues/15011
I tried to workaround this issue using the
azapi_resource
approach as described in that issue, however I ran into the same problem.Doing some digging into the generated
healthcheck-config
configmap output and comparing that to how it functions when it "works" with the CLI, I was able to identify several parameters in the resulting configuration that were not the same.It seems as though the configuration processing applied via
az-cli
here (https://github.com/Azure/azure-cli-extensions/blob/cf183a48b210ff6e7b33af806d4604d9d8c25fdd/src/k8s-extension/azext_k8s_extension/partner_extensions/AzureMLKubernetes.py#L138) is not being applied when done via Terraform.