-
Feature
-
Resolution: Done
-
Major
-
None
-
Strategic Product Work
-
False
-
-
False
-
OCPSTRAT-1131MicroShift Enhancements 2024 for Industrial, Retail and Public Sector edge customers
-
0% To Do, 0% In Progress, 100% Done
-
S
-
0
-
Program Call
-
-
-
Customers need to use multiple namepsaces
-
-
Feature Overview (aka. Goal Summary)
OpenShift Default is not to allow multiple namespaces to access the same hostname. MicroShift inherits that default. The goal of this feature is to give customers a choice and make this configurable.
Goals (aka. expected user outcomes)
- 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.
Requirements (aka. Acceptance Criteria):
- As a MicroShift admin, I want to configure MicroShift to support combining routes from multiple namespaces ("inter-namespace allowed").
Use Cases (Optional):
- Users who compose applications from multiple sources may deploy those to different namespaces, albeit want to expose them using the same hostname and different path.
Out of Scope
n/a
Background
- https://github.com/openshift/enhancements/blob/master/enhancements/ingress/openshift-route-admission-policy.md describes how the flag is exposed in OpenShift.
- https://issues.redhat.com/browse/NE-243
- https://github.com/openshift/api/blob/894b49f57a15cbce3869961e20cd9d52df6f8b0f/operator/v1/types_ingress.go#L918
Customer Considerations
Requested by multiple EAP customers
Documentation Considerations
- Configuration option needs to be documented in the "configuring" book
Interoperability Considerations
None
- is cloned by
-
OCPSTRAT-1068 Enable workload partitioning for MicroShift
- Closed
-
OCPSTRAT-1069 Make MicroShift Ingress configurable
- Closed
-
OCPSTRAT-1073 Introduce cluster id for MicroShift
- Closed
- is related to
-
OCPSTRAT-1413 MicroShift support for Ingress Controller customization
- In Progress
- links to
(1 links to)