Hello All, i have used pulsar-3.3.0 in my Kubernetes cluster, and after giving the security permission for zookeeper, the zookeeper is running now, but the bookie and brokers are still in init state and is not changing. my case seems similar to : https://github.com/apache/pulsar/discussions/17802 have anyone faced this? thanks in advance

init container is waiting for something to be ready. Check the init job log. most of the time, the job is poking zk endpoint.

I commented on https://github.com/apache/pulsar/discussions/17802#discussioncomment-8702647

thanks guys.. for anyone who may be facing this: i had initially installed another version of pulsar in the same namespace, and when i tried this later version, the secrets might have been in conflict. i deleted the old namespace and created again ,and installed pulsar. now it is working.

thanks for sharing @rahul. please also share your findings on https://github.com/apache/pulsar/discussions/17802.

sure will do i have a small doubt..

## And decode any key by using:
  ## kubectl get secret -l component=pulsar-manager -o=jsonpath="{.items[0].data.UI_PASSWORD}" | base64 --decode
  admin:
    ui_username: "pulsar"
    ui_password: "pulsar" # leave empty for random password
    db_username: "pulsar"
    db_password: "pulsar"

but not able to login with that to UI. any idea?

no idea, you can raise an issue to https://github.com/apache/pulsar-helm-chart/issues . please provide exact steps to reproduce from scratch since will help the person who decides to fix it

suree

thanks, great issue report!