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

Using Kubernetes service discovery for ES_SEEDS #6531

Open
mhmtszr opened this issue Sep 18, 2024 · 0 comments
Open

Using Kubernetes service discovery for ES_SEEDS #6531

mhmtszr opened this issue Sep 18, 2024 · 0 comments

Comments

@mhmtszr
Copy link

mhmtszr commented Sep 18, 2024

What are you really trying to do?

Deploying highly available Temporal cluster.

Describe the bug

We are using Kubernetes for our Temporal clusters. We don't want to give only one ip for ES_SEEDS because it can be changed thus we want to give our Kubernetes service definition. But our services contain port as well. I can give empty ES_PORT but still there is ":" character between seeds and port.

We also tried to give all IPs of the cluster seperated by comma(which is we didn't want to), but in this case Temporal server got some errors from Elasticsearch, It tried to send a request like this POST 10.10.10.1,10.10.10.2,10.10.10.3/mapping.

We can make ES_PORT totally optional in both auto-setup and Temporal server. What do you think about this? Do you have any different suggestions to us?

Or we can set ES_SERVER directly that it can overwrite.

@mhmtszr mhmtszr changed the title Making ES_PORT optional for Kubernetes service discovery Using Kubernetes service discovery for ES_SEEDS Sep 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant