azure.cli.core.azclierror.CLIInternalError: Unable to pull clusterdiagnosticchecks helm chart from the registry 'mcr.microsoft.com//azurearck8s/helmchart/stable/clusterdiagnosticchecks:0.2.2': Error: invalid_reference: invalid repository
Describe the bug
Fail to connect k8s cluster with azure arc:
Fail to connect k8s cluster with azure arc:
az connectedk8s connect -g <-HIDE->-test-infra-onboarding-rg6 -n Portal-Cluster --location
Step: 2025-08-11T12-52-19Z: Validating custom access token Step: 2025-08-11T12-52-19Z: Checking Provider Registrations Step: 2025-08-11T12-52-22Z: Setting KubeConfig Step: 2025-08-11T12-52-22Z: Escape Proxy Settings, if passed in Step: 2025-08-11T12-52-23Z: Checking Connectivity to Cluster Step: 2025-08-11T12-52-25Z: Do node validations Step: 2025-08-11T12-52-26Z: Install Kubectl client if it does not exist Step: 2025-08-11T12-52-26Z: Install Helm client if it does not exist Step: 2025-08-11T12-52-26Z: Starting Pre-onboarding-check Step: 2025-08-11T12-52-26Z: Creating folder for Cluster Diagnostic Checks Logs Step: 2025-08-11T12-52-26Z: Get namespace of release: cluster-diagnostic-checks Step: 2025-08-11T12-52-28Z: Determine Helmchart Export Path Step: 2025-08-11T12-52-28Z: Pulling HelmChart: mcr.microsoft.com//azurearck8s/helmchart/stable/clusterdiagnosticchecks, Version: 0.2.2 An exception has occured while trying to execute cluster diagnostic checks container on the cluster. Traceback (most recent call last): File "C:\Users<-HIDE->.azure\cliextensions\connectedk8s\azext_connectedk8s_precheckutils.py", line 217, in executing_cluster_diagnostic_checks_job chart_path = azext_utils.get_chart_path( ^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "C:\Users<-HIDE->.azure\cliextensions\connectedk8s\azext_connectedk8s_utils.py", line 191, in get_chart_path pull_helm_chart( File "C:\Users<-HIDE->.azure\cliextensions\connectedk8s\azext_connectedk8s_utils.py", line 277, in pull_helm_chart raise CLIInternalError( azure.cli.core.azclierror.CLIInternalError: Unable to pull clusterdiagnosticchecks helm chart from the registry 'mcr.microsoft.com//azurearck8s/helmchart/stable/clusterdiagnosticchecks:0.2.2': Error: invalid_reference: invalid repository
During handling of the above exception, another exception occurred:
Traceback (most recent call last): File "C:\Users<-HIDE->.azure\cliextensions\connectedk8s\azext_connectedk8s_precheckutils.py", line 56, in fetch_diagnostic_checks_results executing_cluster_diagnostic_checks_job( File "C:\Users<-HIDE->.azure\cliextensions\connectedk8s\azext_connectedk8s_precheckutils.py", line 407, in executing_cluster_diagnostic_checks_job raise CLIInternalError(f"Failed to execute Cluster Diagnostic Checks Job: {e}") azure.cli.core.azclierror.CLIInternalError: Failed to execute Cluster Diagnostic Checks Job: Unable to pull clusterdiagnosticchecks helm chart from the registry 'mcr.microsoft.com//azurearck8s/helmchart/stable/clusterdiagnosticchecks:0.2.2': Error: invalid_reference: invalid repository
The pre-check result logs logs have been saved at this path: C:\Users<-HIDE->.azure\pre_onboarding_check_logs\Portal-Cluster-Mon-Aug-11-20.52.26-2025. These logs can be attached while filing a support ticket for further assistance.
Related command
az connectedk8s connect -g <-HIDE->-test-infra-onboarding-rg6 -n Portal-Cluster --location
Errors
raise CLIInternalError( azure.cli.core.azclierror.CLIInternalError: Unable to pull clusterdiagnosticchecks helm chart from the registry 'mcr.microsoft.com//azurearck8s/helmchart/stable/clusterdiagnosticchecks:0.2.2': Error: invalid_reference: invalid repository
Issue script & Debug output
This should not be a server side issue, client side construct MCR url in an incorrect way.
Expected behavior
az connectedk8s connect should run successfully.
Environment Summary
{ "azure-cli": "2.70.0", "azure-cli-core": "2.70.0", "azure-cli-telemetry": "1.1.0", "extensions": { "aks-preview": "13.0.0b8", "application-insights": "0.1.14", "azure-devops": "0.21.0", "azure-iot-ops": "0.2.0b2", "bastion": "0.3.0", "config-manager": "1.1.7", "connectedk8s": "1.10.8", "connectedmachine": "0.5.1", "cosmosdb-preview": "1.0.0", "customlocation": "0.1.4", "k8s-configuration": "2.2.0", "k8s-extension": "1.6.7", "monitor-control-service": "1.2.0" } }
Additional context
No response
Thank you for opening this issue, we will look into it.
@yonzhan, any updates on this issue?