@Tommy Johannessen - Welcome to Microsoft Q&A and thanks for reaching out to us.
It is difficult to determine the root cause of the issue. However, there are a few things you can check to troubleshoot the issue.
First, ensure that the Azure Arc-enabled servers Private Link Scope object has been set up correctly. .
Also, check if the connectedk8s
extension is the latest version. You can update the Azure CLI connectedk8s
extension to the latest version by running this command:
az extension update --name connectedk8s
If you haven't installed the extension yet, you can do so by running the following command:
az extension add --name connectedk8s
You can also check if kubeconfig is pointing to the right cluster. Run kubectl config get-contexts
to confirm the target context name. Then set the default context to the right cluster by running kubectl config use-context <target-cluster-name<a href="#doc-pos=3" data-tag-index="1"></a></span>>
.
If you're still unable to connect successfully, generate a troubleshooting log file and then open a support request so we can investigate the problem further.
To generate the troubleshooting log file, run the following command:
az connectedk8s troubleshoot -g <myResourceGroup> -n <myK8sCluster
When you create your support request,
Hope this helps. and please feel free to reach out if you have any further questions.
Please don't forget to "Accept as Answer" and click "Yes" if the above response is helpful, so it can be beneficial to the community.