Epic Goal

The logic in cluster-ingress-operator that installs and configures OSSM 2.y should be updated to install and configure OSSM 3.y.

Why is this important?

The GA release of the OpenShift Gateway API feature will be based on OSSM 3.y.

Planning Done Checklist

The following items must be completed on the Epic prior to moving the Epic from Planning to the ToDo status

• Priority is set by engineering.
• Epic must be Linked to a Parent Feature.
• Target version+ must be set.
• Assignee must be set.
• Enhancement Proposal is Implementable
• No outstanding questions about major work breakdown.
• Are all Stakeholders known? Have they all been notified about this item?
• Does this epic affect SD? Have they been notified? (View plan definition for current suggested assignee)

Acceptance Criteria

• CI - MUST be running successfully with tests automated

Dependencies (internal and external)

1. OSSM 3.0 (currently in Tech Preview).

Previous Work

1. NE-1105.

Open questions

1. Will any further changes be required between OSSM 3.0 Tech Preview and OSSM 3.0 GA?

Done Checklist

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