Currently, the OLMV1 test suite located at olmv1.go does not fully cover OCP-specific functionalities. The OpenShift/origin test suite runs on every PR, so we need to keep it concise while ensuring essential OCP-related components are tested.

To address this, we need to ensure that specific OCP features follow a "happy path" test under olmv1.go, while preventing regressions in key downstream-specific components such as Proxy CA and other OCP-specific functionalities via automated E2E tests.

Scope & Tasks

• Ensure that key OCP-specific (i.e proxy/ca) components are covered under olmv1.go.
• Keep olmv1.go lightweight and efficient, ensuring it only tests the core "does it work" functionality without impacting unrelated PRs.

Acceptance Criteria

• All that is OCP-specific features (e.g., Proxy CA) are tested in olmv1.go under a "happy path" scenario.

Reference Links

🔗 Existing OLMV1 Tests
📖 Extended Test Suite Documentation
🛠️ OLMV1 Testing Guide