<p>I have been using kubernetes (new to it, so I'm sure I made alot of mistakes, or dont understand what I did) and used several tutorials, blogs, etc to install out current environment.</p>

<p>Our backend services are now all insice a kubernetes cluster, using a Azure Cloud Repository for the docker images. </p>

<p>The issue I have is the folowing. I'm leaving the current project, and have to transfer my work to "the new guy". When I do "kubectl get pods" I get a complete list of all the services (docker containers) inside the kubernetes environment.</p>

<p>If "the new guy" does it(on his computer), he gets a empty list, none of my pods are there. (or deployments/services)
He is able to reach all repositories I created in the cluster, he however does not see any of the pods I created.</p>

<p>The thing is, if I log into Azure on his computer, the list is empty, and when he logs into Azure using my computer he has the same list I see.</p>

<p>The pods are therefore somehow computer bound? Yet they run in the cloud...</p>

<p>He has the same rights I have on the entire environment (we are both owners of the azure account/subscription).</p>

<p>My guess is this has something to do with the service principle I have on my computer( or at least I think it's somehow on my computer)? </p>

<p>Can someone explain where my train of thoughts goes wrong here? Or even better, tell me how I can get the same list on his computer as we get on mine??</p>

<p>Thanks in advance.</p>

Rien van der Voorden
<p>If you have done everything correctly regarding his roles <a href="https://learn.microsoft.com/en-gb/azure/role-based-access-control/role-assignments-portal" rel="nofollow noreferrer">Manage access to Azure resources using RBAC and the Azure portal</a>.</p>

<p>I think he's just missing :
<code>az aks get-credentials --resource-group myResourceGroup --name myAKSCluster</code>
Be sure to put correct <code>resource-group</code> and <code>name</code> with the get-credentials.</p>

<p>After that he can test with <code>kubectl get all --all-namespaces</code> to check if all resources across all namespaces are available to him.</p>
