Kubernetes RBAC Generator

Generate Role, ClusterRole, RoleBinding, and ClusterRoleBinding manifests. Easily assign granular API permissions to Users, Groups, or ServiceAccounts.

RBAC Configuration

Metadata

Role / Binding Name

Namespace (ignored for ClusterRole)

Scope

Cluster-Wide Scope (ClusterRole + ClusterRoleBinding)- Unchecked = Role + RoleBinding (namespace-scoped). This generates TWO resources.

Permission Rules

API Groups (csv) — "" for core, "apps", "batch", "networking.k8s.io"

Leave empty or "" for core resources (pods, services). Use "apps" for Deployments.

Resources (csv)

Verbs (csv)

API Groups (csv) — "" for core, "apps", "batch", "networking.k8s.io"

Leave empty or "" for core resources (pods, services). Use "apps" for Deployments.

Resources (csv)

Verbs (csv)

Subjects (Who receives these permissions)

Subject Kind

Subject Name

rbac-configuration.yaml

Kubernetes RBAC Generator

Overview

Generate Kubernetes RBAC (Role-Based Access Control) manifests. RBAC dictates what users, groups, or ServiceAccounts are allowed to do within a cluster or a specific namespace.

Frequently Asked Questions

What is the difference between Role and ClusterRole?

A Role sets permissions within a specific namespace (e.g., granting read access to pods in the 'dev' namespace). A ClusterRole is non-namespaced and can grant access across all namespaces (e.g., a cluster administrator).

How do I bind a Role to a User?

You create a RoleBinding (or ClusterRoleBinding). The binding links the Role (the permissions) to the Subject (the User, Group, or ServiceAccount).