This message was deleted.
# general
s
This message was deleted.
d
Which Helm charts are you using? Are your Zookeeper pods all up and running?
j
Hi David, I'm using chart pulsar-3.0.0 with APP version 2.10.2. and Yes, both pulsar-zookeeper-0 and pulsar-pulsar-manager-7d4f89db7b-tlnxg are running. Thanks
d
StreamNative Charts or Apache Charts?
j
Apache Charts
d
Those have been deprecated, so they might not work as expected.
j
describe the pods, got the following errors: Warning Unhealthy 40m (x3 over 43m) kubelet Readiness probe failed: Get "http://100.64.4.129:8000/api/v1/bookie/is_ready": dial tcp 100.64.4.1298000 connect: connection refused Warning Unhealthy 39m (x4 over 42m) kubelet Liveness probe failed: Get "http://100.64.4.129:8000/api/v1/bookie/state": dial tcp 100.64.4.1298000 Warning Unhealthy 52m kubelet Liveness probe failed: Get "http://100.64.4.130:8080/status.html": dial tcp 100.64.4.1308080 connect: connection refused Warning Unhealthy 52m kubelet Readiness probe failed: Get "http://100.64.4.130:8080/status.html": dial tcp 100.64.4.1308080 connect: connection refused
We were using old version 2.9.4, I'm trying to upgrade to latest version 3.0.0. what you mean by deprecated? Which helm chart should I use instead? Thanks
d
Deprecated, as in no more releases, support etc. https://artifacthub.io/packages/helm/streamnative/pulsar
“This Apache Pulsar Helm Chart has been deprecated and we recommend using streamnative/sn-platform to provision and manage the Apache Pulsar on Kubernetes.”
j
Good morning David! We had a introduction zoom meeting with Marshall Portwood yesterday. He mentioned that you can help me with trouble shooting the issues I am facing. Thank you in advance for your time and help!
I will forward you the email with the logos and describes I had for the issue.
d
Thanks for sharing the information / logs. I am reviewing them now.
Can you share the output of the following commands?
kubectl describe pulsar-bookie-0 -n pulsar
and
kubectl describe pulsar-broker-0 -n pulsar
Thanks
j
Those two should be in the attached email. I will run again
d
ok, let’s switch to communicating via email
j
Sure. Thanks