- Sort Score
- Result 10 results
- Languages All
Results 1 - 2 of 2 for PodSecurityPolicy (0.2 sec)
-
CHANGELOG/CHANGELOG-1.5.md
* Enable the PodSecurityPolicy API (which is not enabled by default): * `--runtime-config=extensions/v1beta1/podsecuritypolicy=true` * Enable the PodSecurityPolicy admission plugin (which is not enabled by default): * `--admission-control=...,PodSecurityPolicy,...` * Use authorization to limit users' ability to use specific PodSecurityPolicy objects **What is the impact?**
Registered: Fri Nov 01 09:05:11 UTC 2024 - Last Modified: Thu Dec 24 02:28:26 UTC 2020 - 136.4K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.4.md
- If you are using the PodSecurityPolicy feature (eg: `kubectl get podsecuritypolicy` does not error, and returns one or more objects), be aware that init containers have moved from alpha to beta. If there are any pods with the key `pods.beta.kubernetes.io/init-containers`, then that pod may not have been filtered by the PodSecurityPolicy. You should find such pods and either delete them or audit them to ensure they do not use features...
Registered: Fri Nov 01 09:05:11 UTC 2024 - Last Modified: Thu Dec 24 02:28:26 UTC 2020 - 133.5K bytes - Viewed (0)