Skip to content

Remove privileged security context from example YAML files#251

Open
piyush302 wants to merge 1 commit intodatainfrahq:masterfrom
piyush302:fix/remove-privileged-security-context
Open

Remove privileged security context from example YAML files#251
piyush302 wants to merge 1 commit intodatainfrahq:masterfrom
piyush302:fix/remove-privileged-security-context

Conversation

@piyush302
Copy link
Copy Markdown
Contributor

Fixes #178

Description

The example YAML files had containerSecurityContext.privileged: true set, which is a security risk and unnecessary for running Druid clusters. Running containers in privileged mode grants them full access to the host, which violates the principle of least privilege.

This PR removes the privileged: true setting from all affected example files while keeping the other security context settings (fsGroup, runAsUser, runAsGroup) intact.


Key changed/added files in this PR
  • e2e/configs/druid-cr.yaml
  • e2e/configs/druid-mmless.yaml
  • tutorials/druid-on-kind/druid-mmless.yaml
  • examples/tiny-cluster-mmless.yaml

@piyush302
Copy link
Copy Markdown
Contributor Author

  • been tested on a real K8S cluster to ensure creation of a brand new Druid cluster works.

@piyush302
Copy link
Copy Markdown
Contributor Author

@AdheipSingh could you please review it . And let me know if anything else is required ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Why do the druid-operator need to run in a privileged security context.

1 participant