azconnected k8s does not work beteeen Tenants
when tring to connect Azure Arc Extension for K8s between 2 Azure Tenants , you get "unauthorized error"
Related command
az connectedk8s connect --name $name --resource-group $rg --location westus2 --correlation-id c18ab9d0-685e-48e7-ab55-12588447b0ed
Logs
This operation might take a while...
Unable to verify connectivity to the Kubernetes cluster.
Error occured while connecting to the kubernetes cluster:
Error Response: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"Unauthorized","reason":"Unauthorized","code":401}
Extension name (the extension in question)
connectedk8s
Detailed Description / Reproducing Steps
-
Go to some Azure Tenant ( for simplicy I will the term "tenant01" here )
-
under the tenant subscription ( I will call it "sub01" that belongs to "tenant01") create AKS Cluster
-
Connect to the cluster : "az aks get-credentials ....." , perform sanity , ensure "kubectl get pods/get nodes" are working
-
at this stage your .kube/config points to the newly created cluster on Tenant 01
-
go to another Tenant / Subscription ( "tenant02/ sub02") and go to new AKS Arc Enabled Cluster
-
change the CLI subscription accordingly : az account set --subscription "sub02"
-
create a new AKS-Arc Enabled cluster , reach the Az CLI Step
-
from the onboarding instruction on Azure Portal you will need to run the CLI
az connectedk8s connect --name $name --resource-group $rg --location westus2 --correlation-id c18ab9d0-685e-48e7-ab55-12588447b0ed
Bug : You are getting Unauthorized 401 :
This operation might take a while...
Unable to verify connectivity to the Kubernetes cluster.
Error occured while connecting to the kubernetes cluster:
Error Response: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"Unauthorized","reason":"Unauthorized","code":401}
additional Info
- Aks ARc was designde in order to onboard K8s cluster from OnPrem/Edge/Cloud-To-Cloud Scenario . it works from local Kind Cluster and from othre Cloud Providers. the fact that you cannot onboard anothre AKS cluster from another Tenant seems limiting.
Thank you for opening this issue, we will look into it.
Adding SErvice attention since this is non-customer reported.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Azure/aks-pm.
Issue Details
when tring to connect Azure Arc Extension for K8s between 2 Azure Tenants , you get "unauthorized error"
Related command
az connectedk8s connect --name $name --resource-group $rg --location westus2 --correlation-id c18ab9d0-685e-48e7-ab55-12588447b0ed
Logs
This operation might take a while...
Unable to verify connectivity to the Kubernetes cluster.
Error occured while connecting to the kubernetes cluster:
Error Response: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"Unauthorized","reason":"Unauthorized","code":401}
Extension name (the extension in question)
connectedk8s
Detailed Description / Reproducing Steps
-
Go to some Azure Tenant ( for simplicy I will the term "tenant01" here )
-
under the tenant subscription ( I will call it "sub01" that belongs to "tenant01") create AKS Cluster
-
Connect to the cluster : "az aks get-credentials ....." , perform sanity , ensure "kubectl get pods/get nodes" are working
-
at this stage your .kube/config points to the newly created cluster on Tenant 01
-
go to another Tenant / Subscription ( "tenant02/ sub02") and go to new AKS Arc Enabled Cluster
-
change the CLI subscription accordingly : az account set --subscription "sub02"
-
create a new AKS-Arc Enabled cluster , reach the Az CLI Step
-
from the onboarding instruction on Azure Portal you will need to run the CLI
az connectedk8s connect --name $name --resource-group $rg --location westus2 --correlation-id c18ab9d0-685e-48e7-ab55-12588447b0ed
Bug : You are getting Unauthorized 401 :
This operation might take a while...
Unable to verify connectivity to the Kubernetes cluster.
Error occured while connecting to the kubernetes cluster:
Error Response: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"Unauthorized","reason":"Unauthorized","code":401}
additional Info
- Aks ARc was designde in order to onboard K8s cluster from OnPrem/Edge/Cloud-To-Cloud Scenario . it works from local Kind Cluster and from othre Cloud Providers. the fact that you cannot onboard anothre AKS cluster from another Tenant seems limiting.
| Author: | tshaiman |
|---|---|
| Assignees: | zhoxing-ms |
| Labels: |
|
| Milestone: | - |
Hi @tshaiman, checking in on this older issue. Sorry it never got a meaningful response. Is this still an active issue for you?