Difference between revisions of "Kubernetes Authentication"

From wikieduonline
Jump to navigation Jump to search
Line 20: Line 20:
 
== Related ==
 
== Related ==
 
* <code>[[kubectl create serviceaccount]]</code>
 
* <code>[[kubectl create serviceaccount]]</code>
* <code>[[kubectl edit configmap aws-auth]]</code>
+
* [[aws-auth]]: <code>[[kubectl edit configmap aws-auth]]</code>
 
* <code>[[gke-gcloud-auth-plugin]]</code>
 
* <code>[[gke-gcloud-auth-plugin]]</code>
 
* <code>[[kind: CertificateSigningRequest]]</code>
 
* <code>[[kind: CertificateSigningRequest]]</code>

Revision as of 12:34, 4 October 2023

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.[1]. Kubernetes determines the username from the common name field in the 'subject' of the cert (e.g., "/CN=your-user").

Authentication options


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


Related

See also

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