-
Notifications
You must be signed in to change notification settings - Fork 16.8k
[incubator/sparkoperator] Use securitycontext
from the chart values for the init and cleanup jobs too
#21539
[incubator/sparkoperator] Use securitycontext
from the chart values for the init and cleanup jobs too
#21539
Conversation
…jobs too Signed-off-by: Wout Maaskant <wout.maaskant@riskident.com>
Hi @scheleaap. Thanks for your PR. I'm waiting for a helm member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
Signed-off-by: Wout Maaskant <wout.maaskant@riskident.com>
/assign @liyinan926 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/lgtm |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: liyinan926, scheleaap, yuchaoran2011 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
… for the init and cleanup jobs too (helm#21539) * Use `securitycontext` from the chart values for the init and cleanup jobs too Signed-off-by: Wout Maaskant <wout.maaskant@riskident.com> * Bump version Signed-off-by: Wout Maaskant <wout.maaskant@riskident.com> Co-authored-by: Wout Maaskant <wout.maaskant@riskident.com>
… for the init and cleanup jobs too (helm#21539) * Use `securitycontext` from the chart values for the init and cleanup jobs too Signed-off-by: Wout Maaskant <wout.maaskant@riskident.com> * Bump version Signed-off-by: Wout Maaskant <wout.maaskant@riskident.com> Co-authored-by: Wout Maaskant <wout.maaskant@riskident.com>
… for the init and cleanup jobs too (helm#21539) * Use `securitycontext` from the chart values for the init and cleanup jobs too Signed-off-by: Wout Maaskant <wout.maaskant@riskident.com> * Bump version Signed-off-by: Wout Maaskant <wout.maaskant@riskident.com> Co-authored-by: Wout Maaskant <wout.maaskant@riskident.com>
… for the init and cleanup jobs too (helm#21539) * Use `securitycontext` from the chart values for the init and cleanup jobs too Signed-off-by: Wout Maaskant <wout.maaskant@riskident.com> * Bump version Signed-off-by: Wout Maaskant <wout.maaskant@riskident.com> Co-authored-by: Wout Maaskant <wout.maaskant@riskident.com> Signed-off-by: Adrien Loiseau <adrien.loiseau@logic-immo.com>
… for the init and cleanup jobs too (helm#21539) * Use `securitycontext` from the chart values for the init and cleanup jobs too Signed-off-by: Wout Maaskant <wout.maaskant@riskident.com> * Bump version Signed-off-by: Wout Maaskant <wout.maaskant@riskident.com> Co-authored-by: Wout Maaskant <wout.maaskant@riskident.com> Signed-off-by: Miguel Mingorance <miguel.mingorance@deliveryhero.com>
Is this a new chart
No
What this PR does / why we need it:
The
securityContext
value of the chart is not applied to the init and cleanup jobs that run when installing, upgrading or deleting the chart. If the cluster has special security requirements (e.g. does not allow containers that run as root), this will cause the jobs to fail.This PR applies
securityContext
to the job containers as well.Checklist
[stable/mychartname]
)@yuchaoran2011 @liyinan926