liveBook · Manning

Authentication

As explained in Kubernetes for Developers

Authentication is the process of verifying or presenting an identity to obtain credentials for accessing a system.

Authentication verifies or presents a user’s identity so the user can obtain credentials to access a Kubernetes cluster through kubectl. Authorization is separate: it determines which actions the authenticated user may perform. A platform IAM role can allow cluster authentication without granting permissions inside the cluster; Kubernetes RBAC can then grant precise access. section 12.6

Keep the operational boundary clear:

  • Use platform IAM to let a user retrieve cluster credentials. section 12.6
  • Use RBAC Roles and RoleBindings to authorize actions within a namespace. section 12.6

How Kubernetes for Developers covers it

How deep it goes
Defines authentication and contrasts it with authorization, stopping short of explaining credential protocol internals.
Examples
Uses GKE credentials, a Google user account, namespace Roles, and Forbidden kubectl commands.
What it assumes
Assumes a configured identity system and Kubernetes platform, while teaching the authentication-authorization boundary explicitly.
What you can do after
Operate kubectl with platform-issued credentials and distinguish authentication failures from RBAC authorization failures.
How it connects
Connects authentication with IAM, kubectl, authorization, and Kubernetes RBAC.

Also explained in

Compare how 34 books explain authentication →

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.