VZ-8024: update fluentd daemonset to meet pod and container security standards #5072
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.
PR to add pod and container security context to fluentd. Tried to run the pod as non-root fluent user, but from local testing, and from some issues reported on the internet and github, it's not feasible (Refs: Some info here and here). The
/var/log
dir mounted from the host node is owned by root, we don't control enough to make this work.After dropping all caps from the fluentd container, had to add back
DAC_OVERRIDE
cap for input tail plugin, found info hereWithout this, some logs were not being sent due to permission problems.
Also updated e2e tests.