You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pod Security Policies were removed in Kubernetes 1.25 and are replaced with Pod Security Admission. I made a quick analysis and, as far as I understood, we need to make the following changes:
Check that the correct profile is applied to non-privileged and user namespaces. E.g., one should not be able to run a root or privileged container in the production namespace.
What artifacts should this produce.
An investigation report, highlighting challenges and changes needed to make Compliant Kubernetes compatible with Kubernetes 1.25.
The text was updated successfully, but these errors were encountered:
What should be investigated.
Pod Security Policies were removed in Kubernetes 1.25 and are replaced with Pod Security Admission. I made a quick analysis and, as far as I understood, we need to make the following changes:
Please proceed as follows:
production
namespace.What artifacts should this produce.
The text was updated successfully, but these errors were encountered: