Goal

• Create an SNO kernel-rt CI lane that's running on non-virtualized metal infrastructure (Equinix, IBM Cloud, etc)

Why is this important?

• The existing kernel-rt lane is HA OpenShift which misses an important category of CI testing for OpenShift, Single Node.
• Anything beyond functional testing cannot happen without SNO running on metal. We do not want to run latency testing as part of something like a presubmit but it should be an option for periodics and release gating jobs as any failure would block Telco customers.

Scenarios

1. ...

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement

Dependencies (internal and external)

1. AWS Metal access in CI

Previous Work (Optional):

1. …

Open questions:

None

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Technical 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>