Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Restrict fluent-bit pod permissions #11657

Merged
merged 2 commits into from Jul 12, 2021
Merged

Conversation

elchead
Copy link
Contributor

@elchead elchead commented Jul 8, 2021

Description
Fluentbit is distributed as a container which must run in the workload cluster as root user in order to collect logs from other containers on the same node. By getting access to that container you can get access to the node file system.

Changes proposed in this pull request:

  • as suggested here: root access is needed but the permissions can be restricted to file access

How it was tested:

  • the logs of the fluent-bit pod were checked
  • in Grafana, the traffic in the logging board was compared to another cluster

Related issue(s)

@kyma-bot kyma-bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Jul 8, 2021
Co-authored-by: Jeremy Harisch <48282931+JeremyHarisch@users.noreply.github.com>
@kyma-bot kyma-bot added the lgtm Looks good to me! label Jul 12, 2021
@jeremyharisch
Copy link
Contributor

/retest

@jeremyharisch
Copy link
Contributor

/test pre-main-kyma-integration-k3s

@kyma-bot kyma-bot merged commit ec6a9e5 into kyma-project:main Jul 12, 2021
@a-thaler a-thaler added the area/logging Issues or PRs related to the logging module (deprecated) label Jul 14, 2021
@a-thaler a-thaler added this to the 2.0-m1 milestone Jul 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/logging Issues or PRs related to the logging module (deprecated) lgtm Looks good to me! size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants