Test Exclusion or Modifications

To prevent indefinite delays, we must define the types of tests we are willing to exclude from the 4vCPU SNO CI lane. Exclusion is defined as tests that are deemed non-critical for basic SNO functionality or are confirmed to be resource-intensive beyond a reasonable minimum requirement, or the test will need some modification.

The team will review and agree on the final list based on the initial CI results, but initial candidates for review include:

• Benchmark/Performance Tests: Any test whose primary goal is to measure peak throughput or latency, as these are expected to be lower on minimum hardware.
• Highly Parallelized Workloads: Tests that spin up numerous pods or complex controllers simultaneously, designed for larger cluster testing.
• Specific Operator Tests: Operators known to have high resource demands that are not core to the SNO runtime (e.g., highly specialized storage or network operators).