You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@pulsar.apache.org by GitBox <gi...@apache.org> on 2020/06/25 13:44:23 UTC

[GitHub] [pulsar-helm-chart] tabalt commented on issue #25: Pods of broker/proxy/recovery init failed when enabled tls

tabalt commented on issue #25:
URL: https://github.com/apache/pulsar-helm-chart/issues/25#issuecomment-649549983


   @sijie  Yes, I have installed cert-manager before installing the Pulsar helm chart.
   ![image](https://user-images.githubusercontent.com/1662442/85725598-d7c76d00-b727-11ea-981d-b6733c30cc34.png)
   The certificate files generated success when I check it, but it did’t generated when the pods of broker/proxy/recovery start.  So the following init script execute failed:
   ```
   /pulsar/keytool/keytool.sh broker ${HOSTNAME}.pulsar-broker.pulsar.svc.cluster.local true;
   ```
   And the following check script will be failed every times:
   ```
   until bin/bookkeeper org.apache.zookeeper.ZooKeeperMain -server pulsar-zookeeper:2281 get /admin/clusters/pulsar; do   echo "pulsar cluster pulsar isn't initialized yet ... check in 3 seconds ..." && sleep 3; done;
   ```


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

For queries about this service, please contact Infrastructure at:
users@infra.apache.org