feat: Enable fluentbit healthcheck #598
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
This PR allows to enable the http Healthcheck that is already implemented in fluentbit and described here: https://docs.fluentbit.io/manual/administration/monitoring#health-check-for-fluent-bit . Since the functionality to add liveness probes already exists it would allow users to setup the liveness probes of fluentbit pods in a way that they query the integrated healthcheck.
Users of the fluent-operator could use this to increase the observability and reliability of their fluentbit instances.
Therefore I believe that this PR is loosely related to #321 . In my eyes it is related in the sense that it allows to enable the healthcheck and theoretically also to expose the healtcheck which could be queried by external tools or setup as kubernetes livenessProbe.
I did not test this in action yet.
Which issue(s) this PR fixes:
RelatesTo #321
Does this PR introduced a user-facing change?
Additional documentation, usage docs, etc.: