Skip to content

fix: Always create the operator ClusterRoleBinding #637

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.

Sign up for GitHub

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

Open
lfrancke wants to merge 1 commit into from
+3 −2
Open

fix: Always create the operator ClusterRoleBinding #637

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions template/deploy/helm/[[operator]]/templates/serviceaccount.yaml.j2
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,9 +10,11 @@ metadata:
annotations:
{{- toYaml . | nindent 4 }}
{{- end }}
{{- end }}
---
apiVersion: rbac.authorization.k8s.io/v1
# This cluster role binding allows anyone in the "manager" group to read secrets in any namespace.
# Grants the operator ServiceAccount the ClusterRole from roles.yaml, which is what lets the
# operator watch and manage its custom resources across the cluster.
kind: ClusterRoleBinding
metadata:
name: {{ include "operator.fullname" . }}-clusterrolebinding
Expand All @@ -26,4 +28,3 @@ roleRef:
kind: ClusterRole
name: {{ include "operator.fullname" . }}-clusterrole
apiGroup: rbac.authorization.k8s.io
{{- end }}