You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I'm using fluent-bit in a cluster along with a few other monitoring tools, one specifically being Prometheus. Fluent-bit has a metrics endpoints on /api/v1/metrics/prometheus and /api/v2/metrics/prometheus which Prometheus can scrape.
I'd like to ensure TLS is enabled on my internal cluster communications, however fluent-bit does not appear to support tls on its monitoring endpoints.
Describe the solution you'd like
The ability to enable TLS on monitoring endpoints.
Describe alternatives you've considered
The only way I can see around this is putting a gateway in front of fluent bit, but I'd rather not when everything else in the cluster supports TLS.
The text was updated successfully, but these errors were encountered:
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days. Maintainers can add the exempt-stale label.
Is your feature request related to a problem? Please describe.
I'm using fluent-bit in a cluster along with a few other monitoring tools, one specifically being Prometheus. Fluent-bit has a metrics endpoints on
/api/v1/metrics/prometheus
and/api/v2/metrics/prometheus
which Prometheus can scrape.I'd like to ensure TLS is enabled on my internal cluster communications, however fluent-bit does not appear to support tls on its monitoring endpoints.
Describe the solution you'd like
The ability to enable TLS on monitoring endpoints.
Describe alternatives you've considered
The only way I can see around this is putting a gateway in front of fluent bit, but I'd rather not when everything else in the cluster supports TLS.
The text was updated successfully, but these errors were encountered: