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

Users should be able to customize the transport service #2644

Closed
barkbay opened this issue Mar 2, 2020 · 1 comment · Fixed by #2691
Closed

Users should be able to customize the transport service #2644

barkbay opened this issue Mar 2, 2020 · 1 comment · Fixed by #2691
Assignees
Labels
>enhancement Enhancement of existing functionality v1.1.0

Comments

@barkbay
Copy link
Contributor

barkbay commented Mar 2, 2020

#2543 introduced a transport service to let Elasticsearch nodes communicate to remote Elasticsearch clusters.

A user should be able to control the spec of this service like we do for the HTTP service (e.g. set the type to LoadBalancer)

@barkbay barkbay added >enhancement Enhancement of existing functionality v1.1.0 labels Mar 2, 2020
@pebrc pebrc self-assigned this Mar 5, 2020
@pebrc
Copy link
Collaborator

pebrc commented Mar 5, 2020

I assume something like this will work:

transport:
   service:
      metadata:
      spec: 

Mirroring the format we use for the http side but leaving out the tls options as we cannot offer TLS configuration on the transport layer (yet)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>enhancement Enhancement of existing functionality v1.1.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants