Skip to content
This repository has been archived by the owner on May 16, 2023. It is now read-only.

Ingress support in Logstash #453

Closed
jnbelo opened this issue Jan 20, 2020 · 7 comments · Fixed by #793
Closed

Ingress support in Logstash #453

jnbelo opened this issue Jan 20, 2020 · 7 comments · Fixed by #793

Comments

@jnbelo
Copy link
Contributor

jnbelo commented Jan 20, 2020

The current Logstash helm chart lacks ingress support. I did find, in a commit that it was initially added but removed soon after.

It states:

Logstash HTTP API shouldn't be exposed externally as Logstash doesn't manage any authentication on this API.
Also as Logstash doesn't support clustering, being able to access this API via a service doesn't make sense.

As far as I saw, the HTTP plugin does support some level of authentication and I really can't see how the lack of clustering support influences this decision. Do these conditions still hold?

@KristapsT
Copy link

Found lacking this same support in the Logstash helm chart.

HTTP Plugin supports HTTP basic authentication, so it shouldn't be an issue to secure it.
Moreover, whoever would wish to have more than HTTP basic auth can ensure that in ingress itself - depending on choice of ingress provider and its integrations, such as client SSL verification, OAuth, etc. - I don't see a reason why helm chart wouldn't give an option to enable HTTP input + add ingress.

@jmlrt jmlrt added the feature label Feb 7, 2020
@jmlrt
Copy link
Member

jmlrt commented Feb 7, 2020

Hi @jnbelo @KristapsT, thanks for reporting this issue. The mentionned commit was about not exposing Logstash API externally. We didn't add the feature to attach an ingress for HTTP plugin yet but may do it later.

@botelastic
Copy link

botelastic bot commented Jul 15, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@camerondavison
Copy link

Is this a good place holder issue for the support coming later? I have been watching it to see when it comes

@botelastic botelastic bot removed the triage/stale label Jul 15, 2020
@jmlrt
Copy link
Member

jmlrt commented Jul 16, 2020

Is this a good place holder issue for the support coming later? I have been watching it to see when it comes

Yes it is, despite we don't plan to work on it in short/mid-term unless someone submit a PR.

@baniga
Copy link

baniga commented Aug 3, 2020

Is there any workaround for this? I do need to expose our Logstash API via an internal load balancer.

@jnbelo
Copy link
Contributor Author

jnbelo commented Aug 20, 2020

Since this seems to be something some people require, I decided to submit a PR. (Sorry for taking months to actually do it, but at the time, I ended up not requiring this feature in my project)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants