ACS (advanced cluster security, aka stackrox) wants to leverage Sippy/CR to help identify regressions. This is a good opportunity to try to get a layered product in our tools.

They run on gke, eks, and several ocp platforms.  They have a combination of prow and github actions, and various testing frameworks but all the prow jobs produce junits that are already consumed in our jobs/junit table.

This card is for a spike to see what's involved in getting them in component readiness.

At a minimum I think we need:

• They use postsubmit jobs (branch-*) instead of only periodics so we'll have to adjust some of our filters.
• Variant registry for gke, eks, etc and identifying stackrox jobs correctly (owner: acs)
• Assign variants/capabilities to their tests

Contact for questions on their said is rh-ee-mtodorov