-
Epic
-
Resolution: Unresolved
-
Blocker
-
None
-
Support restricted Pod Security Standard
-
3
-
False
-
-
False
-
Not Selected
-
To Do
-
ToDo
-
100% To Do, 0% In Progress, 0% Done
-
0
-
0.000
-
Very Likely
-
0
-
None
-
Unset
-
Unknown
Epic Goal
Why is this important?
It is currently expected that by OCP 4.19 (and current master branch 4-dev-preview) that Pod Security Standard set in OpenShift will be restricted from https://issues.redhat.com/browse/OCPSTRAT-487
Our procedure is the following: * we keep it on on master always
Why do we do that?Such that people run into issues and fix them, before we turn it on.
We will need to adjust our products, documentation, and testing accordingly.
Mainly the changes will be related to limiting use of privileged containers across sample apps and the product.
TODOS:
- Make privileged=true configurable in DPA for node agent. Privileged should be the default, but we need to be able to disable this from the DPA
- confirm normal velero manifests backup with CSI/without volumes completes successfully in restricted policy.
- Document that non-privileged node agent will work for datamover but not fs-backup
- Document that shallow copy also won't work in restricted pod env
- Document that to use fs-backup or shallow copy, the cluster security policy must be configured to not require restricted pods
- modify sample apps to conform to the restricted policy.
- set label
Can test restricted Pod Security Standard today in current versions by enabling feature gate or use 4-dev-preview.
Scenarios
Dependencies (internal and external)
User Story:
Foundation for product enhancement.
As a <type of user>
I want <some goal>
so that <value/some reason>
Acceptance Criteria: (Definition of Done)
Defines the scope, what to satisfy before the story is proclaimed as completed. Defines pass/fail criteria.
Verify that…
Functional Acceptance Criteria
Non - Functional Acceptance Criteria
- depends on
-
OADP-5104 Ensure OADP 1.5 install, CSI and DM backups work in pod restricted cluster
- New
- is blocked by
-
OADP-5141 Make OADP work in restricted Pod Security Standard environment
- New
- is depended on by
-
OADP-5157 OADP-1.5.0
- New
-
OADP-5239 Restore Partially Fails Due to container 'restore-wait' Violating PodSecurityContext Constraints
- New
- relates to
-
AUTH-262 Pod Security Admission Integration - Restricted Enforcement
- In Progress
-
OADP-552 Validate OADP with 4.11 and Pod Security Admissions
- Closed
-
OCPSTRAT-487 Pod Security Admission Integration - Restricted Enforcement
- In Progress
- links to