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

[feature] Configuring securityContext at pod level #9783

Open
axel7083 opened this issue Jul 26, 2023 · 10 comments
Open

[feature] Configuring securityContext at pod level #9783

axel7083 opened this issue Jul 26, 2023 · 10 comments

Comments

@axel7083
Copy link
Contributor

axel7083 commented Jul 26, 2023

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 👍.

@chensun
Copy link
Member

chensun commented Aug 11, 2023

What are the versions of KFP and SDK you're using? Also what container image being used for the component?

@dashanji
Copy link

dashanji commented Oct 9, 2023

Agree +1.

I'm using KFP v2, and it look like we can't add the securityContext to the IR YAML.

Copy link

github-actions bot commented Jan 8, 2024

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.

@github-actions github-actions bot added the lifecycle/stale The issue / pull request is stale, any activities remove this label. label Jan 8, 2024
@rimolive
Copy link
Member

rimolive commented Mar 6, 2024

PR #10538 will handle this

@stale stale bot removed the lifecycle/stale The issue / pull request is stale, any activities remove this label. label Mar 6, 2024
Copy link

github-actions bot commented May 6, 2024

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.

@github-actions github-actions bot added the lifecycle/stale The issue / pull request is stale, any activities remove this label. label May 6, 2024
Copy link

This issue has been automatically closed because it has not had recent activity. Please comment "/reopen" to reopen it.

@rimolive
Copy link
Member

/reopen

Copy link

@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.

@google-oss-prow google-oss-prow bot reopened this May 28, 2024
@github-actions github-actions bot removed the lifecycle/stale The issue / pull request is stale, any activities remove this label. label May 29, 2024
Copy link

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.

@github-actions github-actions bot added the lifecycle/stale The issue / pull request is stale, any activities remove this label. label Jul 29, 2024
@juliusvonkohout
Copy link
Member

/lifecycle frozen

@google-oss-prow google-oss-prow bot added lifecycle/frozen and removed lifecycle/stale The issue / pull request is stale, any activities remove this label. labels Jul 31, 2024
@github-project-automation github-project-automation bot moved this to Needs triage in KFP Runtime Triage Aug 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Status: Needs triage
Development

No branches or pull requests

5 participants