Epic Goal

• Expose a configuration option to control the namespace ownership check in the router to allow multiple routes/ingress resources to use the same hostname but different paths.

Why is this important?

• Users who compose applications from multiple plugins may deploy those to different namespaces.

Scenarios

1. As a MicroShift admin, I want to configure MicroShift to support combining routes from multiple namespaces ("inter-namespace allowed").

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. https://github.com/openshift/enhancements/blob/master/enhancements/ingress/openshift-route-admission-policy.md describes how the flag is exposed in OpenShift.
2. https://issues.redhat.com/browse/NE-243
3. https://github.com/openshift/api/blob/894b49f57a15cbce3869961e20cd9d52df6f8b0f/operator/v1/types_ingress.go#L918 

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>