Skip to content
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

Azure connected clusters fails, unable to connect cluster to Azure via arc as part of IoT Ops setup #30943

Open
peredwardsson opened this issue Mar 4, 2025 · 5 comments
Labels
Auto-Assign Auto assign by bot bug This issue requires a change to an existing behavior in the product in order to be resolved. Configure az configure/config Connected Kubernetes customer-reported Issues that are reported by GitHub users external to the Azure organization. Service Attention This issue is responsible by Azure service team.

Comments

@peredwardsson
Copy link

Describe the bug

Attempting to connect a cluster via connectedk8s as part of the Azure IoT Ops suite I'm getting stuck when connecting my local k3s cluster to Azure Arc.

Related command

az connectedk8s connect -g <rg> -n <clustername> -l westeurope --subscription <subid> --tags System.Object[] --disable-auto-upgrade --enable-oidc-issuer --enable-workload-identity 

Same error with:

az connectedk8s connect -g <rg> -n <clustername> -l westeurope  --subscription <subid> --tags System.Object[] --disable-auto-upgrade

Errors

Issue script & Debug output

debug.txt

Expected behavior

The cluster is connected via Arc and shows up in the Azure portal.

Environment Summary

azure-cli 2.70.0 core 2.70.0 telemetry 1.1.0 Extensions: azure-iot-ops 1.2.0 connectedk8s 1.10.6 k8s-extension 1.6.3 ssh 2.0.6 Dependencies: msal 1.31.2b1 azure-mgmt-resource 23.1.1 Python location 'C:\Program Files\Microsoft SDKs\Azure\CLI2\python.exe' Config directory 'C:\Users<user>.azure' Extensions directory 'C:\Users<user>.azure\cliextensions' Python (Windows) 3.12.8 (tags/v3.12.8:2dc476b, Dec 3 2024, 19:30:04) [MSC v.1942 64 bit (AMD64)] Legal docs and information: aka.ms/AzureCliLegal Your CLI is up-to-date.

Additional context

No response

@peredwardsson peredwardsson added the bug This issue requires a change to an existing behavior in the product in order to be resolved. label Mar 4, 2025
@yonzhan
Copy link
Collaborator

yonzhan commented Mar 4, 2025

Thank you for opening this issue, we will look into it.

@microsoft-github-policy-service microsoft-github-policy-service bot added customer-reported Issues that are reported by GitHub users external to the Azure organization. IoT Service Attention This issue is responsible by Azure service team. Auto-Assign Auto assign by bot IoT/CLI Configure az configure/config labels Mar 4, 2025
@microsoft-github-policy-service microsoft-github-policy-service bot added Azure CLI Team The command of the issue is owned by Azure CLI team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Mar 4, 2025
Copy link
Contributor

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Azure/azure-iot-cli-triage.

@yonzhan yonzhan added Connected Kubernetes and removed question The issue doesn't require a change to the product in order to be resolved. Most issues start as that IoT/CLI Azure CLI Team The command of the issue is owned by Azure CLI team IoT labels Mar 4, 2025
Copy link
Contributor

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @akashkeshari.

@peredwardsson
Copy link
Author

In case it's interesting, I'm running this script when it fails.

@peredwardsson
Copy link
Author

Maybe duplicate of Azure/azure-cli-extensions#6637

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Auto-Assign Auto assign by bot bug This issue requires a change to an existing behavior in the product in order to be resolved. Configure az configure/config Connected Kubernetes customer-reported Issues that are reported by GitHub users external to the Azure organization. Service Attention This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

3 participants