Syphixs opened a new issue #90: URL: https://github.com/apache/pulsar-helm-chart/issues/90
**Describe the bug** I tried to create a new cluster from scratch but the zookeeper won't start. For testing I changed component sizes to: 1 x proxy 1 x broker 2 x zookeeper 3 x bookies 1 x recovery I configured cert-manager to provide self signed certs with JKS and PKCS12. Log: [conf/zookeeper.conf] Applying config dataDir = /pulsar/data/zookeeper [conf/zookeeper.conf] Adding config secureClientPort = 2281 [conf/zookeeper.conf] Adding config serverCnxnFactory = org.apache.zookeeper.server.NettyServerCnxnFactory processing /pulsar/certs/zookeeper/tls.crt : len = 1724 processing /pulsar/certs/zookeeper/tls.key : len = 3272 processing /pulsar/certs/ca/ca.crt : len = 1302 Importing keystore /pulsar/zookeeper.p12 to /pulsar/zookeeper.keystore.jks... Warning: The JKS keystore uses a proprietary format. It is recommended to migrate to PKCS12 which is an industry standard format using "keytool -importkeystore -srckeystore /pulsar/zookeeper.keystore.jks -destkeystore /pulsar/zookeeper.keystore.jks -deststoretype pkcs12". Certificate was added to keystore processing /pulsar/zookeeper.keystore.jks : len = 3795 processing /pulsar/zookeeper.truststore.jks : len = 1038 Current server id 1 Error: Could not find or load main class # **To Reproduce** Steps to reproduce the behavior: 1. helm install --set initialize=true pulsar -f values.yaml ./pulsar **Expected behavior** Succesfully init cluster with near default values **Screenshots**  **Desktop (please complete the following information):** - OS: IOS - Kubernetes: 1.18.6 - Helm: 3.3.1 **Additional context** Add any other context about the problem 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
