-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Ingress support in Logstash #453
Comments
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. |
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. |
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. |
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. |
Is there any workaround for this? I do need to expose our Logstash API via an internal load balancer. |
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) |
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:
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?
The text was updated successfully, but these errors were encountered: