-
Story
-
Resolution: Unresolved
-
Minor
-
None
-
None
-
8
-
True
-
This story is blocked by https://issues.redhat.com/browse/COS-1360
-
False
Overview
This body of work is derived from the spike please refer to this story https://issues.redhat.com/browse/CFE-384
Tasks
- Well documented README - describing how to deploy SPO
- Ensure that the node-observability-operator deploys normally
- Update the SCC
allowPrivilegedContainer: false
- Ensure that this section is removed from the daemonset
SecurityContext: &corev1.SecurityContext{ Privileged: &privileged, },
- Implement the logic to check for the SPO (fully operational)
- Implement the logic to create the RawSeLinuxProfile CR
- Validate that the nodes have been updated accordingly
- Ensure the daemonset (and agents) deploy correctly
- Delete all references to the SPO and CR before allowing profiling to start
- Ensure E2E tests are updated with the dependency of the SPO and RawSeLinuxProfile CR
Acceptance Criteria
- Documentation approval
- QE approval
- All unit tests passing
- Updated E2E tests
- CI (prow) step updated with SPO dependency and CR
- clones
-
CFE-384 [R&D] As a developer I want to investigate the use of the openshift security-profile-operator to deploy custom SELinux scripts into each node so that I can mitigate the need for executing a container as privileged
- Closed