frankjkelly opened a new issue #173: URL: https://github.com/apache/pulsar-helm-chart/issues/173
**Describe the bug** When we try to deploy two Pulsar instances in different K8S namespaces in the same K8S Cluster we get ``` 16:58:22 Error: rendered manifests contain a resource that already exists. Unable to continue with install: ClusterRole "platform-pulsar-broker-clusterrole" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; annotation validation error: key "meta.helm.sh/release-namespace" must equal "cogito-saas": current value is "datamigration" 16:58:22 time="2021-11-08T21:58:20Z" level=fatal msg="exit status 1" ``` Although there is support here via `rbac.limit_to_namespace` https://github.com/apache/pulsar-helm-chart/blob/master/charts/pulsar/templates/broker-cluster-role-binding.yaml#L23-L27 There is still a clusterrole defined here https://github.com/apache/pulsar-helm-chart/blob/master/charts/pulsar/templates/broker-cluster-role-binding.yaml#L43-L47 **Expected behavior** Pulsar supports having pulsar instances with the same name in different K8S namespaces -- 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