Docs update: Ensure users are not confused by Kubernetes cluster roles
Problem to solve
customer pointed out that our docs says the following in here: https://docs.gitlab.com/ee/user/project/clusters/#attribute-based-access-control-abac
gitlab ServiceAccount
gitlab-admin ClusterRoleBinding
but in https://docs.gitlab.com/ee/user/project/clusters/#adding-an-existing-kubernetes-cluster it shows gitlab-admin
for both.
original report (internal): https://gitlab.zendesk.com/agent/tickets/119246
Further details
Copied from slack discussion
Daniel Gruesso the service account is called
gitlab
, I believe the cluster role name is actuallycluster-admin
$kubectl get clusterroles
NAME AGE
admin 12d
certmanager-cert-manager 12d
cloud-provider 12d
cluster-admin 12d
edit 12d
gce:beta:kubelet-certificate-bootstrap 12d
gce:beta:kubelet-certificate-rotation 12d
gce:cloud-provider 12d
ingress-nginx-ingress 12d
kubelet-api-admin 12d
Proposal
Update the add existing cluster section to be correct and match the rest of the docs.
Edited by Cynthia "Arty" Ng