frankjkelly edited a comment on pull request #174:
URL: https://github.com/apache/pulsar-helm-chart/pull/174#issuecomment-964569367


   Seems to be working in my local Minikube
   
   With `rbac.limit_to_namespace: true`
   
   ```
    $ kubens cogito
   Context "minikube" modified.
   Active namespace is "cogito".
    $ kubectl get pods
   NAME                           READY   STATUS      RESTARTS   AGE
   pulsar-bookkeeper-0            1/1     Running     0          4m3s
   pulsar-bookkeeper-init-jtk42   0/1     Completed   0          4m3s
   pulsar-broker-0                1/1     Running     0          4m3s
   pulsar-proxy-0                 1/1     Running     0          4m3s
   pulsar-pulsar-init-6bvw4       0/1     Completed   0          4m3s
   pulsar-zookeeper-0             1/1     Running     0          4m3s
    $ kubens cogito2
   Context "minikube" modified.
   Active namespace is "cogito2".
    $ kubectl get pods
   NAME                           READY   STATUS      RESTARTS   AGE
   pulsar-bookkeeper-0            0/1     Init:0/1    0          45s
   pulsar-bookkeeper-init-xsg22   0/1     Completed   0          45s
   pulsar-broker-0                0/1     Init:0/2    0          45s
   pulsar-proxy-0                 0/1     Init:0/2    0          45s
   pulsar-pulsar-init-sbpxx       1/1     Running     0          45s
   pulsar-zookeeper-0             1/1     Running     0          45s
   ```
   
   With `rbac.limit_to_namespace: false` I get one namespace OK and the second 
   ```
   Error: rendered manifests contain a resource that already exists. Unable to 
continue with install: ClusterRole "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 "cogito2": current value is "cogito"
   ```


-- 
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


Reply via email to