liveBook · Manning

Service account

As explained in Kubernetes for Developers

A Kubernetes ServiceAccount is an identity and credential object intended for workloads that access the Kubernetes API.

A Kubernetes ServiceAccount is an identity and credential object for workloads that need to access the Kubernetes API. It represents code running in the cluster rather than a human user. section 12.6

Grant workload access by creating a ServiceAccount and using it as the subject of an RBAC binding. For example, a monitoring Pod can receive permission to inspect another Deployment’s Pod status. section 12.6

Keep workload and human access separate:

  • Use ServiceAccounts for services and other code running in the cluster. section 12.6
  • Use federated User identities for human developers instead of distributing ServiceAccount certificates. section 12.6
  • Avoid downloaded ServiceAccount credentials for developers because they can remain valid after the developer is suspended in the identity system. section 12.6

How Kubernetes for Developers covers it

How deep it goes
Explains the workload identity role and RBAC-binding pattern, while stopping short of a complete ServiceAccount manifest.
Examples
Uses a monitoring Pod inspecting another Deployment and contrasts distributed developer certificates with federated human identities.
What you can do after
Apply it via RBAC to authorize in-cluster code while preserving identity-system control for human access.
How it connects
Connects ServiceAccounts with Kubernetes API access, RBAC, Pods, Deployments, identity federation, and OIDC.

Also explained in

Compare how 10 books explain service account →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Kubernetes for Developers. The section links point to the parts of the book it draws on.