-
Notifications
You must be signed in to change notification settings - Fork 45
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
Custom service #113
Comments
The es-operator creates a service for each ElasticsearchDataSet (eds) that you define. This is mostly intended for the operator to communicate with Elasticsearch API, but ofc you can also use it for ingress (I think). We currently don't allow you to e.g. change this to a Your config snippet suggest that you both create an ALB for ingress AND an ELB for service type LoadBalancer. I don't know if this is intentional or what purpose it serves, but if an ingress is enough then you can create an ingress resource that points to the service created by es-operator. I hope this clarifies it a bit. |
First of all, thank you a lot for your quick response 👍 So far I was trying to overwrite the service and creating the ingress ( add my own label selectors), but knowing that I can not change
My previous configuration was wrong (using only ingress or service loadbalancer) Anyway, I will comment tomorrow if I succeed or not to deploy my |
I think we can close that. I succeed to create my ingress and a service that target the
So so far, I use the Thx again |
Question
I have an overall question about
es-operator
. I am migrating from the official ES helm chart (for the data nodes the other node are still deploy with helm). However I am stuck to the last part:configuring my ingress
On the official helm chart, I can setup an ingress / services like:
Which will create 2 services (one load balancer and one headless)
However I can not (or find a way) to setup this load balancer correctly. From what I saw from the code, the operator need to own the service and will create a NodePort service.
Does there is anyway to solve that ?
What I will do in the meantime is deploy some coordinate nodes with the load balancer, so I can access the Elasticsearch cluster (or do that on the master node for testing)
The text was updated successfully, but these errors were encountered: