Add separate headless service for ZooKeeper statefulset#649
Merged
lhotari merged 15 commits intoapache:masterfrom Feb 20, 2026
Merged
Add separate headless service for ZooKeeper statefulset#649lhotari merged 15 commits intoapache:masterfrom
lhotari merged 15 commits intoapache:masterfrom
Conversation
- the previous cluster ip service will only connect to pods in ready state
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Previously there was a single service which would connect to unready pods (
publishNotReadyAddresses: true). It's better to have 2 services: 1 with cluster ip and another "headless" (clusterIP: None) withpublishNotReadyAddresses: true.When Zookeeper clients connect, they would use the cluster ip service that connects to a health pod. The headless service is only used for zookeeper-to-zookeeper communications since it's used in the statefulset as the service name and will determine the hostnames for the pods.
The benefit of this change is that brokers and bookies won't try to connect to a ZK pod that is failing or hasn't started up.