pixime opened a new issue #6135: Unable to deploy on GKE, blocked at bookie.yaml step URL: https://github.com/apache/pulsar/issues/6135 I'm trying to deploy pulsar on gke according to the Deploy pulsar components chapter in the documentation (https://pulsar.apache.org/docs/en/deploy-kubernetes/#deploy-pulsar-components). I use the apache-pulsar-2.5.0/deployment/kubernetes/google-kubernetes-engine yaml source directory. Steps : - kubectl create -f zookeeper.yaml : OK, ok 3 replicated pods are running - kubectl create -f cluster-matadata.yaml : OK, completed - Kubectl create -f bookie.yaml failed. I got the following error many times in the bookie-autorecovery logs: Opening socket connection to server localhost/127.0.0.1:2181. Will not attempt to authenticate using SASL (unknown error). As the zookeeper client StatefulSetport is set to 2181, I suppose that the bookie-autorecovery is unable to connect to zookeeper. Naturally it ends by a CrashLoopBackOff. Notice also that the bookie pods seem to be stuck, no logs. My gke configuration is: - 3 nodes - n1-standard-4 - no autoscaling at the moment - europe-west1 Any idea ?
---------------------------------------------------------------- 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: [email protected] With regards, Apache Git Services
