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

Enable SecurityContext on container level #749

Closed
Shwethamuralikrishnaa opened this issue Aug 4, 2022 · 16 comments
Closed

Enable SecurityContext on container level #749

Shwethamuralikrishnaa opened this issue Aug 4, 2022 · 16 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@Shwethamuralikrishnaa
Copy link

Shwethamuralikrishnaa commented Aug 4, 2022

Is your feature request related to a problem? Please describe.
We are not able to define containerSecurityContext, this causes efs-csi-driver containers to get flagged by security scanner.

Describe the solution you'd like in detail
The chart must support the containerSecurityContext.

Describe alternatives you've considered

Additional context

@pierluigilenoci
Copy link
Contributor

@wongma7 @Ashley-wenyizha @RomanBednar can you please take a look?

@k8s-triage-robot
Copy link

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR 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 Nov 24, 2022
@pierluigilenoci
Copy link
Contributor

/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 Nov 28, 2022
@pierluigilenoci
Copy link
Contributor

@mskanth972 @mjsoyeon could you please take a look?
@Ashley-wenyizha @dschunack @lmouhib who should I ask for feedback?

@dschunack
Copy link
Contributor

/assign @jsafrane

@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 Mar 20, 2023
@pierluigilenoci
Copy link
Contributor

/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 Mar 20, 2023
@pierluigilenoci
Copy link
Contributor

@jsafrane, any news on this?

@mskanth972
Copy link
Contributor

Hi @pierluigilenoci, thanks for bringing here, we will plan to work on this soon and add the respected fields readOnlyRootFilesystem , allowPrivilegeEscalation under the security context.

@jsafrane
Copy link
Contributor

jsafrane commented May 3, 2023

/unassign
Please don't assign me to random issues without my consent.

@RyanStan
Copy link
Contributor

RyanStan commented May 15, 2023

/kind enhancement

@k8s-ci-robot
Copy link
Contributor

@RyanStan: The label(s) kind/enchancement cannot be applied, because the repository doesn't have them.

In response to this:

/kind enchancement

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@RyanStan
Copy link
Contributor

/kind feature

@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label May 15, 2023
@mskanth972
Copy link
Contributor

mskanth972 commented May 17, 2023

Closing the issue as PR for enabling security context for container level is merged and will mark it in the coming release.

@mskanth972
Copy link
Contributor

/close

@k8s-ci-robot
Copy link
Contributor

@mskanth972: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

8 participants