Difference between revisions of "Kubernetes Authentication"

From wikieduonline
Jump to navigation Jump to search
 
(3 intermediate revisions by the same user not shown)
Line 17: Line 17:
 
* <code>[[kubectl config set-credentials]]</code>
 
* <code>[[kubectl config set-credentials]]</code>
  
 +
== Activities ==
 +
* [[Access Kubernetes REST API using default token]]
  
 
== Related ==
 
== Related ==
Line 24: Line 26:
 
* <code>[[kind: CertificateSigningRequest]]</code>
 
* <code>[[kind: CertificateSigningRequest]]</code>
 
* [[Kubernetes Authorization]]
 
* [[Kubernetes Authorization]]
 +
* [[EKS Authentication]]
 +
* [[kubectl create token]]
  
 
== See also ==
 
== See also ==
* {{kubectl config}}
 
* {{Kubernetes service account}}
 
 
* {{Kubernetes Authentication}}
 
* {{Kubernetes Authentication}}
  
 
[[Category:K8s]]
 
[[Category:K8s]]

Latest revision as of 16:58, 31 October 2023

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

Accounts[edit]

  • 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[edit]


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

Activities[edit]

Related[edit]

See also[edit]

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