Epic Goal

• The security profiles operator is used to manage security profiles which are applied across nodes of a cluster. The goal of this epic is to expand the scope of SPO so that it's available on P/Z/A.

Why is this important?

• This is important because customers running clusters of different architectures are limited to to what can be done with the MCO since SPO isn't available. Also, some features of compliance operator depend on SPO.

Scenarios
1. SPO can be installed on P/Z/A and custom security profile can be applied.

Acceptance Criteria

• SPO can be installed on P/Z/A
• Custom security profiles can be applied
• Validation tests for SPO pass on all 4 arches
• Any potential issues with multi-arch clusters identified

Dependencies (internal and external)
1. Compliance Team

Previous Work (Optional):
1. Compliance Operator
2. DISA-Stig profile for Power (ongoing)

Open questions::

• None

Done Checklist

• CI - For new features (non-enablement), existing Multi-Arch CI jobs are not broken by the Epic
• Release Enablement: <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR orf GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - If the Epic is adding a new stream, downstream build attached to advisory: <link to errata>
• QE - Test plans in Test Plan tracking software (e.g. Polarion, RQM, etc.): <link or reference to the Test Plan>
• QE - Automated tests merged: <link or reference to automated tests>
• QE - QE to verify documentation when testing
• DOC - Downstream documentation merged: <link to meaningful PR>
• All the stories, tasks, sub-tasks and bugs that belong to this epic need to have been completed and indicated by a status of 'Done'.