Difference between revisions of "Kind: ClusterRoleBinding"
Jump to navigation
Jump to search
Line 8: | Line 8: | ||
name: read-secrets-global | name: read-secrets-global | ||
subjects: | subjects: | ||
− | - kind: Group | + | - [[kind: Group]] |
name: manager # Name is case sensitive | name: manager # Name is case sensitive | ||
apiGroup: rbac.authorization.k8s.io | apiGroup: rbac.authorization.k8s.io | ||
[[roleRef:]] | [[roleRef:]] | ||
− | kind: ClusterRole | + | [[kind: ClusterRole]] |
name: secret-reader | name: secret-reader | ||
apiGroup: [[rbac.authorization.k8s.io]] | apiGroup: [[rbac.authorization.k8s.io]] |
Revision as of 12:41, 31 October 2023
apiVersion: rbac.authorization.k8s.io/v1 # This cluster role binding allows anyone in the "manager" group to read secrets in any namespace. kind: ClusterRoleBinding metadata: name: read-secrets-global subjects: - kind: Group name: manager # Name is case sensitive apiGroup: rbac.authorization.k8s.io roleRef: kind: ClusterRole name: secret-reader apiGroup: rbac.authorization.k8s.io
https://kubernetes.io/docs/reference/access-authn-authz/rbac/#clusterrolebinding-example
roleRef RoleBinding
Related
See also
Advertising: