Kvindo™ Cloud Docs
A Kubernetes User Role is a reusable RBAC rule that defines a set of permissions inside a cluster — which API groups, resources, verbs, and namespaces are allowed. It is not a binding on its own; attach it to one or more Kubernetes Users (via their roleIds) to grant them those permissions. In the cluster this materializes as a Role + RoleBinding per listed namespace — or as a ClusterRole + ClusterRoleBinding when spec.namespaces is ["*"].
• API groups — the Kubernetes API groups the rule covers (spec.apiGroups; "" is the core group)
• Resources — the resource types allowed (spec.resources, e.g. pods, services)
• Verbs — the actions allowed (spec.verbs, e.g. get, list, watch, create)
• Namespaces — the namespaces the rule applies to (spec.namespaces); use ["*"] for a cluster-wide role
• Node Group prerequisite — the cluster needs at least one Node Group with a nonzero node count before this Role can successfully reconcile
| UI Name | API / kc name | Terraform name | Optional | Format | Default | Is read only | Description |
|---|---|---|---|---|---|---|---|
| API groups | spec.apiGroups |
spec.api_groups |
No | list of strings | — | No | API groups covered; "" is the core group |
| Resources | spec.resources |
spec.resources |
No | list of strings | — | No | Resource types, e.g. pods, services |
| Verbs | spec.verbs |
spec.verbs |
No | list of strings | — | No | Allowed actions, e.g. get, list |
| Namespaces | spec.namespaces |
spec.namespaces |
No | list of strings | — | No | Namespaces the rule applies to (a Role + RoleBinding per namespace); ["*"] creates a cluster-wide ClusterRole + ClusterRoleBinding instead |
A read-only role over pods and services in the default namespace.
Terraform
Python SDK
kc CLI
Resource docs
Examples
More in this section