pipelines
pipelines copied to clipboard
[feature] Configuring securityContext at pod level
Feature Area
/area backend /area sdk
/area components
What feature would you like to see?
Being able to configure securityContext in v2.
What is the use case or pain point?
When using an image from dockerhub for example, which has not a default user 0 in the @dsl.component(base_image="<non-root-image>"), when trying to write to OutputPath, got the following error:
failed to execute component: unable to create directory "/minio/mlpipeline/v2/artifacts/pipeline-name/uuid/custom-function" for output artifact "model": mkdir /minio: permission denied
Details
Worflow support the security at spec level Workflow Pod Security Context.
Love this idea? Give it a 👍.
What are the versions of KFP and SDK you're using? Also what container image being used for the component?
Agree +1.
I'm using KFP v2, and it look like we can't add the securityContext to the IR YAML.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
PR #10538 will handle this
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically closed because it has not had recent activity. Please comment "/reopen" to reopen it.
/reopen
@rimolive: Reopened this issue.
In response to this:
/reopen
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-sigs/prow repository.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
/lifecycle frozen