Epic Goal

Implement a mechanism that, once a user request a Gateway to be deployed, this Gateway reflects the current Openshift Topology.

In case of HA Topology, deploy with a minimum of 2 replicas. In case of non-HA topology, deploy with a minimum of 1 replica.

Customize the maximum replicas to be, for now, a non disruptive number for customers (eg.: maximum of 3 replicas).

Why is this important?

Some customers has been asking about customizing the number of replicas for Gateway API on Openshift. While we don't have an API for it today, it is important for the adoption that we guarantee that some best practices are followed, like deploying a Gateway with more than 1 replica.

Proposed "how":

During some spike for the customization of Gateway API parameters, we have found that Sail Operator can be used to set sane defaults of a Gateway class.

This way, we want to make CIO detect the platform that is being executed, and send the right parameters to Sail Operator to provision the Gateway Class with best practices applied to its default config.

More information at: https://docs.google.com/document/d/10utpc7zGhBlrMCzPr8MZpLAAI6qVXFXtTWZuxfITNy0/edit?tab=t.0

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)
  1. Please use the “Discussion Needed: Service Delivery Architecture Overview” checkbox to facilitate the conversation with SD Architects. The SD architecture team monitors this checkbox which should then spur the conversation between SD and epic stakeholders. Once the conversation has occurred, uncheck the “Discussion Needed: Service Delivery Architecture Overview” checkbox and record the outcome of the discussion in the epic description here.
  2. The guidance here is that unless it is very clear that your epic doesn’t have any managed services impact, default to use the Discussion Needed checkbox to facilitate that conversation.

Additional information on each of the above items can be found here: Networking Definition of Planned

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement
  details and documents.

...

Dependencies (internal and external)

1.

...

Previous Work (Optional):

1. …

Open questions::

1. …

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>