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.

Sign up for GitHub

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

Jump to bottom

Feat: Add support to define (overwrite) SecurityContext #1437

Open
cbugneac-nex opened this issue Feb 12, 2024 · 2 comments · May be fixed by #1438
Open

Feat: Add support to define (overwrite) SecurityContext #1437

cbugneac-nex opened this issue Feb 12, 2024 · 2 comments · May be fixed by #1438
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@cbugneac-nex
Copy link

cbugneac-nex commented Feb 12, 2024 •
edited

Describe the solution you'd like
One of requirements from our Cyber security team is to drop capabilities where possible to improve security posture (reduce attack surface) for containers running in k8s.

In values.yaml file to define something like (example):

...
securityContext:
  capabilities:
    drop:
      - ALL
  runAsNonRoot: true
  allowPrivilegeEscalation: false
  seccompProfile:
    type: RuntimeDefault

Anything else you would like to add:
At the moment, this is not possible as it's hardcoded https://github.com/kubernetes-sigs/secrets-store-csi-driver/blob/main/charts/secrets-store-csi-driver/templates/secrets-store-csi-driver.yaml#L113

Environment:

  • Secrets Store CSI Driver version: (use the image tag): v1.4.1
  • Kubernetes version: (use kubectl version): EKS version 1.26.12
@cbugneac-nex cbugneac-nex added the kind/feature Categorizes issue or PR as related to a new feature. label Feb 12, 2024
@cbugneac-nex cbugneac-nex changed the title Add support to define (overwrite) SecurityContext Feat: Add support to define (overwrite) SecurityContext Feb 12, 2024
@cbugneac-nex cbugneac-nex linked a pull request Feb 12, 2024 that will close this issue
Open
3 tasks
@aramase aramase mentioned this issue Mar 19, 2024
Closed
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 13, 2024
@Constantin07
Copy link

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Milestone
No milestone
4 participants
@Constantin07 @k8s-ci-robot @k8s-triage-robot @cbugneac-nex