@RunLLM Can you explain the configuration option

publishNotReadyAddresses

on bookkeeper?

The

publishNotReadyAddresses

option in BookKeeper (and Kubernetes services) allows server addresses to be published to DNS and become discoverable before the pods have passed their readiness probe. This enables components like the coordinator to connect and determine health before the bookie is marked as "ready" by Kubernetes. This is particularly useful for stateful services like BookKeeper, where early discovery can help with cluster coordination and health checks, even if the bookie is not yet fully ready to serve traffic. According to Enable publishNotReadyAddresses on server service, this setting is used to propagate server addresses early for discovery purposes. Would you like more detail on how to configure this in your deployment? Sources: - Enable publishNotReadyAddresses on server service 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

Btw. For Pulsar brokers, there would be a need in the Pulsar Helm chart for publishNotReadyAddresses, explained in https://github.com/apache/pulsar-helm-chart/issues/437

Thanks you, I'll go through that. That's what I was wondering, since the option is only for bookeepers and was wondering if something similar was available for brokers.

Yes, we'd need it for brokers too so that we can avoid the problem explained in the issue.

Ok that makes sense, thanks!