Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Zk clientservice cannot be declared external #572

Open
Ella-eln opened this issue Oct 1, 2023 · 1 comment · May be fixed by #576
Open

Zk clientservice cannot be declared external #572

Ella-eln opened this issue Oct 1, 2023 · 1 comment · May be fixed by #576

Comments

@Ella-eln
Copy link

Ella-eln commented Oct 1, 2023

The operator creates 3 services: adminServerService, clientservice and headless. Out of which, only adminServerService could be declared as external (available outside of the cluster via nodeport).
This creates a problem when deploying an app that uses the zk as state manager because other apps may require access to that state.

For example, Solr using the operator, zk operator is used to create a quorum that keeps tab on Solr's nodes. In order to write data to Solr one must contact the quorum (done through client port) and obtain a list of available nodes. Without this ability, Solr is practically unavailable.

This problem could be solved relatively simply by adding the option to make clientservice external to the operator

@yortch
Copy link

yortch commented Oct 23, 2023

I also have a similar use case to be able to access zookeeper as a stand alone component and connect to it from outside the Kubernetes cluster. I created a NodePort service (for port 2181) and was able to access it and connect to it using zkCli. My only question is as to whether the leader election port (3888) and quorum port (2888) need to be exposed as well?

@idolaman idolaman linked a pull request Nov 20, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants