Epic Goal

• Make SPO perform well in large environments

Why is this important?

• While SPO is more-or-less feature ready, there are issues around scalability and performance that might hit OCP customers. This epic tries to address them

Scenarios

1. As a developer, I want to record a large application
2. As an OCP administrator, I want a frictionless experience deploying OCP

Acceptance Criteria

• SPO must be able to record a seccomp and/or a SELinux profile for a non-trivial application. At the moment, the apps that are recorded as part of SPO's e2e suite are more or less toy apps (e.g. an nginx deployment doing nothing)
• SPO can be installed on an OCP cluster without interfering with the cluster's functionality. This concerns mostly the webhooks that SPO is using at the moment

Dependencies (internal and external)

1. ..

Previous Work (Optional):

1. CMP-933

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>