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

Usage of PSP for controlling safe/unsafe sysctls isn't documented #3174

Closed
php-coder opened this issue Mar 31, 2017 · 6 comments
Closed

Usage of PSP for controlling safe/unsafe sysctls isn't documented #3174

php-coder opened this issue Mar 31, 2017 · 6 comments
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@php-coder
Copy link
Contributor

It turns out that user can annotate PSP with security.alpha.kubernetes.io/sysctls annotation to specify "whitelist of allowed safe and unsafe sysctls in a pod spec". It isn't documented.

@liggitt
Copy link
Member

liggitt commented Mar 31, 2017

I'd rather see them graduate to fields before getting officially documented and used
@pweil-

@pweil-
Copy link

pweil- commented Apr 3, 2017

Ok. @php-coder let's discuss what else needs to be done on the roadmap to graduate the feature and get this worked into a card for PM

@php-coder
Copy link
Contributor Author

I found that the usage of safe/unsafe sysctls are documented here: https://kubernetes.io/docs/concepts/cluster-administration/sysctl-cluster/ But its usage doesn't relate to PSP at all.

@sttts Could you explain how PSP strategy (pkg/security/podsecuritypolicy/sysctl) is correlated with the current behavior when admin need to pass --experimental-allowed-unsafe-sysctls option to the kubelet?

@sttts
Copy link
Contributor

sttts commented Nov 24, 2017

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/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 Feb 22, 2018
@php-coder
Copy link
Contributor Author

The documentation was added in #7600 and is available at https://kubernetes.io/docs/concepts/cluster-administration/sysctl-cluster/#podsecuritypolicy-annotations

/close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

7 participants