hashicorp / hashicorp/vault-helm
PodSecurityPolicy: policy/v1beta1 will be removed in k8s v1.25
- Dominant language
- Shell
- Stars
- 1.3k
- Forks
- 898
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 1
Description
**Is your feature request related to a problem? Please describe.**
https://kubernetes.io/docs/reference/using-api/deprecation-guide/#psp-v125
_PodSecurityPolicy in the policy/v1beta1 API version will no longer be served in v1.25, and the PodSecurityPolicy admission controller will be removed.
PodSecurityPolicy replacements are still under discussion, but current use can be migrated to 3rd-party admission webhooks now._
Additional context: https://kubernetes.io/blog/2021/04/06/podsecuritypolicy-deprecation-past-present-and-future/
_Kubernetes 1.21 starts the deprecation process for PodSecurityPolicy. As with all feature deprecations, PodSecurityPolicy will continue to be fully functional for several more releases. The current plan is to remove PSP from Kubernetes in the 1.25 release._
**Describe the solution you'd like**
Deprecate the usage of PodSecurityPolicy until k8s v1.25 arrives, evaluate and switch to alternatives
Contributor guide
Research direction
Start with the linked Kubernetes deprecation guide and blog post, then inspect the chart for its PodSecurityPolicy usage. Determine which supported alternative applies and define the migration scope; the work is done when the chart no longer relies on the deprecated policy/v1beta1 API before Kubernetes 1.25.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- infrastructure, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100