bsheltonihs opened a new issue #230:
URL: https://github.com/apache/pulsar-helm-chart/issues/230
**Is your feature request related to a problem? Please describe.**
I am using argo-cd to deploy on openshift using these helm charts. The issue
I have is when I enable functions the `broker-rbac` tries to create
`ClusterRole` and `ClusterRoleBinding`. The error I get is `Cluster level
ClusterRoleBinding "pulsar-functions-worker" can not be managed when in
namespaced mode` . This is because at openshift is managed at the enterprise
level and they don't allow this. However, you guys have addressed this same
issue with the `broker-role` and `broker-rolebinding` but adding the `{{- if
.Values.rbac.limit_to_namespace }}` logic in the
`broker-cluster-role-binding.yaml` template.
**Describe the solution you'd like**
I would like the same logic `{{- if .Values.rbac.limit_to_namespace }}` used
for the `broker-role` in the template `broker-cluster-role-binding.yaml` file
to be applied to the `function` section of the template `broker-rbac.yaml` file
**Describe alternatives you've considered**
The only other clear alternative that I see is set `resource.exclusions`
within argo-cd to exclude `ClusterRole` and `ClusterRoleBinding`. Then create
my own chart to create the `role` and `rolebinding` (Which isn't viable long
term)
**Additional context**
Add any other context or screenshots about the feature request here.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
