Use a unique ClusterRoleBinding name to account for hosted mode

Prior to this, the governance-policy-framework ClusterRoleBinding would have the same name for every hosted cluster on the hosting/management cluster. The generated ManifestWork objects would overwrite each other since it did not append to the subjects array. Using a unique name per hosted cluster like the config-policy-controller does will resolve this. Relates: https://issues.redhat.com/browse/ACM-4486 Signed-off-by: mprahl <[email protected]>
open-cluster-management-io · Mar 23, 2023 · cce56fa · cce56fa
1 parent 2022a3a
commit cce56fa
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/pkg/addon/policyframework/manifests/managedclusterchart/templates/cluster_role_binding.yaml b/pkg/addon/policyframework/manifests/managedclusterchart/templates/cluster_role_binding.yaml
@@ -3,7 +3,7 @@
 apiVersion: rbac.authorization.k8s.io/v1
 kind: ClusterRoleBinding
 metadata:
-  name: {{ include "controller.rolename" . }}-binding
+  name: ocm:{{ .Release.Namespace }}:{{ include "controller.fullname" . }}
   labels:
     app: {{ include "controller.fullname" . }}
     chart: {{ include "controller.chart" . }}