Thank you for your patience while we are reviewing your query!
As mentioned in the document, we support two ways to attach a Kubernetes cluster to Azure Machine Learning workspace, using Azure CLI or studio UI.
https://learn.microsoft.com/en-us/azure/machine-learning/how-to-attach-kubernetes-to-workspace?view=azureml-api-2&tabs=cli#how-to-attach-a-kubernetes-cluster-to-azure-machine-learning-workspace
Comparison of KubernetesCompute and legacy AksCompute targets
With the Azure Machine Learning CLI/Python SDK v1, you can deploy models on AKS by using the legacy AksCompute
target. Both the KubernetesCompute
and AksCompute
targets support AKS integration, but the support approach is different.
The following table summarizes the key differences:
Capability | AksCompute (legacy) | KubernetesCompute |
---|---|---|
Use the CLI/SDK v1 | Yes | No |
Use the CLI/SDK v1 | Yes | No |
Use the CLI/SDK v2 | No | Yes |
Set up training | No | Yes |
Apply real-time inference | Yes | Yes |
Apply batch inference | No | Yes |
Access new features for real-time inference | No new features development | Active roadmap available |
In consideration of these differences, and the overall Machine Learning evolution to use the CLI/SDK v2, the recommended approach is to use Kubernetes compute target (KubernetesCompute
) for AKS model deployment.
As per my understanding, when using Terraform, the default attachment type for AKS clusters in Azure ML is AksCompute, not KubernetesCompute.
Hope this helps!
Let me know if you have any further queries!
If the comment is helpful, please click "upvote" to let us know.