Creating User and Role in Kubernetes and Binding Them via RBAC

Wed, 23 Sep 2026 00:00:00 +0000

In Kubernetes there are no “users” in the traditional sense — there are ServiceAccounts and certificates, bound to roles through RBAC. Without proper configuration, anyone holding a kubeconfig gets full access to the cluster. Below is the complete cycle: create a ServiceAccount, define permissions, bind them, and verify.

Creating ServiceAccount and Generating kubeconfig

Start by creating a ServiceAccount in the target namespace:

kubectl create serviceaccount devops-sa -n staging

To generate a kubeconfig, extract the token from secrets and build the config file:

kubectl whoami and Service Account Permission Checks

Wed, 02 Sep 2026 00:00:00 +0000

When deploying an application to Kubernetes, the most common failure is a service account that cannot do what it should. Permission denied when creating a secret, rejection on list pods, refusal on update. kubectl whoami and kubectl auth can-i let you quickly identify exactly who cannot do what.

kubectl whoami plugin

Note

kubectl whoami is not a built-in kubectl command. It is a plugin from krew or a standalone binary. Install with kubectl krew install whoami or download from GitHub.

Rbac on Lead DevOps

Creating User and Role in Kubernetes and Binding Them via RBAC

Creating ServiceAccount and Generating kubeconfig

kubectl whoami and Service Account Permission Checks

kubectl whoami plugin