Kubernetes Authentication

https://kubernetes.io/docs/reference/access-authn-authz/authentication/

Accounts

• Service accounts are users managed by the Kubernetes API. They are bound to specific namespaces, and created automatically by the API server or manually through API calls. Service accounts are tied to a set of credentials stored as Secrets, which are mounted into pods allowing in-cluster processes to talk to the Kubernetes API.
• Users: "normal" user accounts cannot be added via an API call, any user that presents a valid certificate signed by the cluster's certificate authority (CA) is considered authenticated.. Kubernetes determines the username from the common name field in the 'subject' of the cert (e.g., "/CN=your-user").

Authentication options

• Certificates
• Bearer tokens
• Authenticating proxy

Authorization: Bearer 31ada4fd-adec-460c-809a-9e56ceb75269

• A user store like Keystone or Google Accounts

• kubectl config set-credentials

Activities

• Access Kubernetes REST API using default token

Related

• kubectl create serviceaccount
• aws-auth: kubectl edit configmap aws-auth
• gke-gcloud-auth-plugin
• kind: CertificateSigningRequest
• Kubernetes Authorization
• EKS Authentication
• kubectl create token

See also

• Kubernetes Authentication, kubectl create serviceaccount, kubectl get serviceaccounts, CertificateSigningRequest, aws-auth, bearer tokens, EKS Authentication

https://kubernetes.io/docs/reference/access-authn-authz/authentication/#users-in-kubernetes