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

Support configuring security context #456

Closed
ywk253100 opened this issue Dec 2, 2019 · 3 comments
Closed

Support configuring security context #456

ywk253100 opened this issue Dec 2, 2019 · 3 comments

Comments

@ywk253100
Copy link
Collaborator

Currently, the containers in Harbor run as specific user(user ID 10000 or 999), and the user cannot be changed because some directives such as https://github.com/goharbor/harbor/blob/release-1.10.0/make/photon/registry/Dockerfile#L9. This prevents the supporting for configuringrunAsUser.
For other security context directives https://kubernetes.io/docs/concepts/policy/pod-security-policy/#example-policies, we need more test to verify they can work as expected.

There is already a PR #266 from community for the security context supporting

@ywk253100 ywk253100 self-assigned this Dec 2, 2019
@NickHes
Copy link

NickHes commented Jun 18, 2023

@ywk253100 Any plans to support this in the future? With Kubernetes 1.24 reaching EOL and clusters migrating to 1.25 with the new policies I suspect the need for this will grow. Currently we cannot run Harbor with the new policies enabled. If you are open for PR's for this we could most certainly take a look.

Copy link

github-actions bot commented Feb 8, 2024

This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days.

@github-actions github-actions bot added the Stale label Feb 8, 2024
Copy link

This issue was closed because it has been stalled for 30 days with no activity. If this issue is still relevant, please re-open a new issue.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants