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
UPDATE 2021-11-26: Pod Security Standards are now officially supported and documented. They allow putting namespaces in the baseline, restricted or privileged security profiles.
Privileged seems to be what we need for "system" Pods, e.g., fluentd, falco.
Baseline seems to be what we need for "application" and user Pods, e.g., Harbor, Elasticsearch, Kibana.
What artifacts should this produce.
A demo of the future approach that solves the problems that PodSecurityPolicies currently do.
Action items to migrate to Pod Security Standards
The text was updated successfully, but these errors were encountered:
What should be investigated.
PodSecurityPolicies are planned to be deprecated in Kubernetes 1.21 and removed in Kubernetes 1.25.
UPDATE 2021-11-26: Pod Security Standards are now officially supported and documented. They allow putting namespaces in the baseline, restricted or privileged security profiles.
Privileged seems to be what we need for "system" Pods, e.g., fluentd, falco.
Baseline seems to be what we need for "application" and user Pods, e.g., Harbor, Elasticsearch, Kibana.
What artifacts should this produce.
The text was updated successfully, but these errors were encountered: