lhotari opened a new issue, #437: URL: https://github.com/apache/pulsar-helm-chart/issues/437
**Is your feature request related to a problem? Please describe.** Pulsar brokers use Zookeeper for publishing the membership to other brokers. The Pulsar load manager will detect a new broker and assign new namespace bundles to the new broker. One of the gaps with Pulsar and k8s is that the broker registers itself to Zookeeper and the broker pod cannot be accessed before the broker pod's readiness probe check has passed and k8s makes it ready and available in DNS. This delay will cause a short service disruption for all topics belonging to the namespace bundles that have been assigned to the new broker. **Describe the solution you'd like** The way to mitigate this is to have a separate ClusterIP service to be used for lookups and have a headless service with "publishNotReadyAddresses: true". This is a common way to address the problem. One example of this is the Bitnami Zookeeper Helm chart, https://github.com/bitnami/charts/tree/main/bitnami/zookeeper/templates there's svc.yaml and svc-headless.yaml The DNS names of the 2 services will be different. Since clients don't need to know the direct DNS names of the brokers, it's better to change the current headless service to be the ClusterIP service and add a new headless service for handling the stable names of the brokers. Admin scripts that connect directly to individual brokers might break, but that's could be made clear in the release notes when this feature is released. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
