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
When using Fluent Bit in_http plugin the only approved method is a POST. However when using Fluent Bit with an ingress on K8s across major Cloud Providers the default health checks use a GET on top of the Kubernetes service which can cause problems if you want to expose Fluent Bit's in_http plugin
Ideally, Fluent Bit can have the following: A new parameter allow_healthcheck which gives the ability to a user to issue a GET request on the same port and get a 200 response. The reason to have a new parameter is that if adding to exsiting in_http it could break logic where a GET fails today
The text was updated successfully, but these errors were encountered:
When using Fluent Bit in_http plugin the only approved method is a POST. However when using Fluent Bit with an ingress on K8s across major Cloud Providers the default health checks use a GET on top of the Kubernetes service which can cause problems if you want to expose Fluent Bit's in_http plugin
Ideally, Fluent Bit can have the following: A new parameter
allow_healthcheck
which gives the ability to a user to issue a GET request on the same port and get a 200 response. The reason to have a new parameter is that if adding to exsiting in_http it could break logic where a GET fails todayThe text was updated successfully, but these errors were encountered: