-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
az connectedk8s connect has been failed #2077
Comments
After setting HELM registry URL by manually, it works. SET HELMREGISTRY=azurearcfork8s.azurecr.io/batch1/stable/azure-arc-k8sagents:0.2.4 |
Hi @akashkeshari , could you please help with this issue ? Thanks |
Hi @Dongbumlee Can you run the following command and share the output so that we can look into the issue: To unblock you, run the following commands:
Thanks, |
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @akashkeshari. |
I am hitting the same issue. The workaround does not work for me. Environment Summary
The output:
Then set the environment based on that path:
Debugging the script, it looks like: def get_release_namespace(kube_config, kube_context): it looks like it is attempting to enumerate the helm repo which returns an empty array, which the json parser fails on.
|
@ooeygui , Can you please share the version of helm installed on your machine? |
@akashkeshari Thanks for the reply - I'm using helm3 installed using
|
This issue has been fixed. Please update the connectedk8s extension to version 0.2.4 and try again: Let us know if you still face this issue. @ooeygui , I think we already had a discussion over email. You may also switch to the new version of connectedk8s (0.2.4). |
@akashkeshari Thank you - this specific issue no longer manifests for me with your fixes. |
This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az connectedk8s connect Extension Name: connectedk8s. Version: 0.2.1.
Errors:
To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.
az connectedk8s connect --name {} --resource-group {} -l {} --debug
Expected Behavior
Environment Summary
Additional Context
The text was updated successfully, but these errors were encountered: