Provision a ClusterRole If Missing
A 2-step recipe with Kubernetes. We can help you get access.
Recipe · 2 steps
Provision a ClusterRole If Missing
with Kubernetes · Identity & Access Management
Create a ClusterRole with the supplied policy rules unless it already exists.
- List ClusterRoles so the flow can tell an existing role from a missing one by name, rather than provoking a 409 conflict on create.
- Create the ClusterRole with the supplied policy rules. ClusterRoles are cluster-scoped and take effect once bound via a ClusterRoleBinding.
What you'll need to have ready
- clusterRoleName: Name of the ClusterRole to provision.
- rules: Policy rules granting verbs on resources within API groups. Each rule carries verbs, apiGroups, and resources arrays.
- labels: Labels to apply to the ClusterRole, such as an installer or owner tag.
- labelSelector: Optional label selector narrowing the listing to an installer's own roles. ClusterRole listing supports label selection only, so the branch below matches the ta
For your developer
Arazzo workflow kubernetes:provision-cluster-role, 2 operations: listClusterRoles → createClusterRole. Specs on APIs.io.