Issue with k8s.io/docs/tasks/configure-pod-container/migrate-from-psp/

[jglick]

This page would be more helpful if it listed actual PodSecurityPolicy YAML corresponding (to the extent possible) to the new baseline and restricted levels.

[sftim]

@jglick maybe if that page linked to the example PSP list in https://kubernetes.io/docs/concepts/security/pod-security-standards/#policy-instantiation? Would that help?

(BTW, those “levels” aren't entirely new - the 3 pod security standards have been in Kubernetes docs since May 2020)

[jglick]

Yes, that is exactly what I was looking for. Adding a link would be helpful.

[sftim]

/sig docs
/sig security
/triage accepted
/language en
/priority backlog

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

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.

[jglick]

There is https://kubernetes.io/docs/reference/access-authn-authz/psp-to-pod-security-standards/ which is probably good enough. I still find it somewhat clearer to just see stock PSP YAML examples so that you can check whether an existing PSP resources was simply copied from one of these. Unfortunately the link you referenced in #30823 (comment) is no longer useful because the links to the PSP example files (though not the files themselves) was deleted: #33512 (comment)

[sftim]

For the current v1.27 docs, I'm happy with how they look.

(my individual opinion, but as a tech lead for docs) I'd be willing to accept changes against the v1.24 (and older) docs to put those examples back, and then revise https://kubernetes.io/docs/concepts/security/pod-security-policy/ to make it even easier to find the relevant pages that still have the documentation.

All this would need now is people to volunteer to do that work.

[sftim]

There's a technical blocker to having example PodSecurityPolicies in the current docs: we validate the example manifests, and PSP is no longer part of Kubernetes.