-
### Experienced behaviour
Should be the mode enabled once modern BPF is selected.
However the templating sets the wrong value, and the podsecuritypolicies are not adapting to the least privileged mo…
-
csi-driver-lvm chart is still using `PodSecurityPolicy` which is removed in current k8s version
https://kubernetes.io/docs/concepts/security/pod-security-policy/
-
### Description
PodSecurityPolicy will be removed from the Kubernetes API in version 1.25. We'll have to either remove this feature from the provider, or adapt it to only run against APIs < 1.25.
…
-
## Summary
Hi team,
PodSecurityPolicy API, initially deprecated in Kubernetes v1.21, was [entirely removed i](https://kubernetes.io/blog/2022/08/04/upcoming-changes-in-kubernetes-1-25/#podsecuri…
-
### Is your feature request related to a problem? Please describe.
Pod security polices are deprecated since 1.21. However, k0s still allows configuring a default PodSecurityPolicy and the security m…
-
I think there could be various ways to do this, but my first hunch goes towards allowing to pass a PodSecurityPolicy name to bind each component to.
-
I am using kubent version 0.7.2, and it is still making calls to the deprecated podsecuritypolicies API.
**Environment**:
- Kubernetes version: 1.28.10-gke.1075001
- `kubent` version: 0.7.2
**…
-
Presently Voyager Operator does not respect pod security policies and fails to create HAProxy pods, if cluster has 'restricted' policies enabled by default (and require to run as non-root).
Could y…
-
Commit f27f119d759fd43197a1670917461aa96c17cd88 prevents the platform from being deployed with `helm`, the error message being:
```console
services "backend-cosv" already exists
```
- Caused b…
-
Our [current privileged PodSecurityPolicy](https://github.com/kinvolk/lokomotive/blob/v0.2.0/assets/lokomotive-kubernetes/bootkube/resources/charts/kubernetes/templates/psp-privileged.yaml) grants ver…