GitHub user lhotari added a comment to the discussion: Error from server (BadRequest): container "pulsar-broker" in pod "pulsar-broker-0" is waiting to start: PodInitializing
There was on reply on Pulsar Slack to check the logs of the init jobs that initialize the cluster. It's not very useful to do any analysis without the logs. It's useful to check Kubernetes events and logs Tips related to following k8s events in the console: ``` # events for ALL namespaces (fine for a local minikube or Docker Desktop k8s) kubectl get events --sort-by=.lastTimestamp -A # tailing all events kubectl get events --sort-by=.lastTimestamp -A --watch ``` Getting logs, `pulsar-broker-0` in `pulsar` namespace as example: ``` kubectl -n pulsar logs pulsar-broker-0 # getting previous logs, for the previously crashed pod kubectl -n pulsar logs pulsar-broker-0 -p ``` In this case, I'd check the init job logs (append `-n pulsar` to the command if you have a specific command, check the jobs with `kubectl get jobs` to see if they have different names). ``` kubectl logs job/pulsar-pulsar-init kubectl logs job/pulsar-pulsar-init -p kubectl logs job/pulsar-bookie-init kubectl logs job/pulsar-bookie-init -p ``` You could use a k8s UI such as `k9s` on command line or [OpenLens](https://github.com/MuhammedKalkan/OpenLens)/[Lens](https://k8slens.dev/) for the desktop. That makes things a lot users to begin with. GitHub link: https://github.com/apache/pulsar/discussions/17802#discussioncomment-8702647 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
