Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat/fix(rbac): use generated RBAC in kustomize and helm, grant access to leases #1540

Merged
merged 8 commits into from
May 20, 2024
Prev Previous commit
Next Next commit
chore(kustomize): move rolebinding to a separate file, include kubebu…
…ilder role
  • Loading branch information
weisdd committed May 19, 2024
commit 284c9f70614baaa33ab8a68c19c3a5d3b1c7de79
10 changes: 9 additions & 1 deletion deploy/kustomize/base/kustomization.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -4,4 +4,12 @@ resources:
- serviceaccount.yaml
- service.yaml
- deployment.yaml
- rbac.yaml
- rolebinding.yaml
- ../../../config/rbac/role.yaml
patches:
- target:
kind: ClusterRole
patch: |
- op: replace
path: /metadata/name
value: grafana-operator-permissions
268 changes: 0 additions & 268 deletions deploy/kustomize/base/rbac.yaml

This file was deleted.

12 changes: 12 additions & 0 deletions deploy/kustomize/base/rolebinding.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
name: grafana-operator-permissions
subjects:
- kind: ServiceAccount
name: grafana-operator-controller-manager
namespace: default
roleRef:
kind: ClusterRole
name: grafana-operator-permissions
apiGroup: rbac.authorization.k8s.io