<p>I have this strange situation, how I can solve this problem ?</p>
<pre><code>ubuntu@anth-mgt-wksadmin:~$ kubectl get nodes
error: the server doesn't have a resource type &quot;nodes&quot;

ubuntu@anth-mgt-wksadmin:~$ kubectl cluster-info
To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.
error: the server doesn't have a resource type &quot;services&quot;

ubuntu@anth-mgt-wksadmin:~$ kubectl cluster-info dump
Error from server (Forbidden): users &quot;xxx@xxx.it&quot; is forbidden: User system:serviceaccount:gke-connect:connect-agent-sa&quot; cannot impersonate resource &quot;users&quot; in API group &quot;&quot; at the cluster scope
</code></pre>
<p>I think that the problem has been generated by this following apply searching a way to connect the admin cluster to Cloud Console but how to rollback ?</p>
<pre><code>USER_ACCOUNT=foo@example.com
cat &lt;&lt;EOF &gt; /tmp/impersonate.yaml
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  name: gateway-impersonate
rules:
- apiGroups:
  - &quot;&quot;
  resourceNames:
  - ${USER_ACCOUNT}
  resources:
  - users
  verbs:
 - impersonate
 - --
 - apiVersion: rbac.authorization.k8s.io/v1
 - kind: ClusterRoleBinding
metadata:
  name: gateway-impersonate
roleRef:
  kind: ClusterRole
  name: gateway-impersonate
  apiGroup: rbac.authorization.k8s.io
subjects:
- kind: ServiceAccount
  name: connect-agent-sa
  namespace: gke-connect
EOF
# Apply impersonation policy to the cluster.
kubectl apply -f /tmp/impersonate.yaml
</code></pre>

andrea ciuffoli
<p>I have copied the admin.conf file from one admin cluster node to the admin workstation and renamed to kubeconfig</p>
<pre><code>root@anth-admin-host1:~# cat /etc/kubernetes/admin.conf apiVersion: v1 clusters:
</code></pre>
