Goal

• ROUTER_DENIED_DOMAINS is available within the HAProxy Router to be configured and thus needs to be exposed
• ROUTER_ALLOWED_DOMAINS is available within the HAProxy Router to be configured and thus needs to be exposed

Why is this important?

These options are heavily used by clients on OCP 3.11 and similar requests have come to enable these already configurable options for 4.X

Scenarios

1.  Clients have multiple Domains in their corporate network and application may only use some of them, they need to have a way to define the set of allowed or denied domains

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>