<p>I'm new into Kubernetes and playing around with the Kubernetes-RBAC. I want restrict access to my cluster for different users. As I unterstood Service-Accounts meant for intra-cluster processes running inside pods, which want to authenticate against the API.</p>

<p>So should I use User-Accounts for Buildservers and access from outside the cluster via a kubeconfig-file? Or what are the best practices in this case?</p>

<p>Is it bad to use Service-Accounts to access the cluster from remote?</p>

Feralus
<p>You should use Kubernetes' ordinary user authentication system for authenticating automation agents that run outside the cluster.  Service accounts are only usable by pods running inside the cluster (unless you go very far out of your way to "borrow" a service account token).  You can do things like set up a <a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.14/#rolebinding-v1-rbac-authorization-k8s-io" rel="nofollow noreferrer">RoleBinding</a> to give special permission to create and delete Kubernetes objects to your CD system's user.</p>
