Skip to content
Prev Previous commit
Next Next commit
Got the feeling from kubectl get clusterrole ...
that having access control rules, in particular cluster scoped,
lying around without knowing where they come from
will be unmaintainable over time. Labels show up nicely in describe.
  • Loading branch information
solsson committed Aug 5, 2017
commit 35974266ae938856f3a254b12308b1a99e67e5e7
4 changes: 4 additions & 0 deletions rbac-namespace-default/events-watcher.yml
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,8 @@ kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1beta1
metadata:
name: events-watcher
labels:
origin: github.com_Yolean_kubernetes-kafka
rules:
- apiGroups:
- ""
Expand All @@ -16,6 +18,8 @@ kind: ClusterRoleBinding
apiVersion: rbac.authorization.k8s.io/v1beta1
metadata:
name: kafka-events-watcher
labels:
origin: github.com_Yolean_kubernetes-kafka
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
Expand Down
4 changes: 4 additions & 0 deletions rbac-namespace-default/node-reader.yml
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,8 @@ kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1beta1
metadata:
name: node-reader
labels:
origin: github.com_Yolean_kubernetes-kafka
rules:
- apiGroups:
- ""
Expand All @@ -16,6 +18,8 @@ kind: ClusterRoleBinding
apiVersion: rbac.authorization.k8s.io/v1beta1
metadata:
name: kafka-node-reader
labels:
origin: github.com_Yolean_kubernetes-kafka
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
Expand Down