>_ IzzyLab

Topic breakdown

RBAC in Kubernetes is built from two parts: a Role describes a SET of permissions (in its rules — apiGroups, resources, and the verbs), while a RoleBinding ties that role to a subject (a user, group, or ServiceAccount). Verbs are granular: list (enumerate a collection) and get (read a specific object by name) are different permissions, and one doesn't imply the other. The key point: roleRef.name in the binding must exactly match the name of an existing Role — a reference to a nonexistent role doesn't cause a creation error, but it grants no permissions either. Objects in the file are separated by ---.

What's checked

  1. both manifests are valid (kubeconform)
  2. Role allows get and list on pods
  3. RoleBinding references pod-reader

What it looks like