Purpose

Ensure you have test coverage for all supported versions of OSD, as well as the upcoming version. The team has validated that sufficient and effective system monitoring, alerting and automated testing (CI/CD OSD) are in place.

The OSDe2e pipeline is owned by the Service Delivery team (led by Jeremy Eder) today. To onboard on the pipeline, kindly allow at least 7 days before your release date, reach out #forum-managed-tenants slack channel

• This process is documented here: https://github.com/openshift/osde2e/blob/main/docs/Addons.md

Note:

• This only applies to Addons (MT-SRE) and CS-SRE, not to SaaS (App-SRE); if your service does not contain (or otherwise relies on) a Kubernetes Operator deployed via the Add-Ons flow, then this task does not apply: please close out as "Won't Do". 
• This process does NOT replace your existing QE. It is meant to ensure that your software works on OSD specifically. 

Responsible: Engineering, Quality Engineering, Service Delivery CI/CD 

Informed: Service Delivery should be informed with a PASS result (or green light) to give approval for the final MR.

Deliverable: You have run the OSDE2E in a local environment and get a PASS result, or you have onboarded the OSDE2E pipeline and getting green lights.

Expected Duration: a few days

Channel to get help: #forum-managed-tenants slack channel

Planned Changes: Interoperability Testing team is working with Service Deliver, QE and engineering teams to cover OSD testing, upgrade testing and (TBD integration testing) for all cloud services; once they are engaged with your/individual program team, this should be covered, and this task will not longer be required separately. 

Phase: (MT-SRE) recommend completing this for Service Preview but it is not compulsory. You should assess the risk of not completing this task with MT-SRE