Description of problem: Openshift 4.1 doesn't allow enablement of wildcard routes on default router. The IngressController object doesn't have any attribute which would allow that. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Create route with wildcardPolicy set to Subdomain Actual results: Route is not admitted with message wildcard routes are not allowed Expected results: Route will be exposed, and all unmatched requests to subdomain will be forwarded to correct service. Additional info: We haven't found any workaround, when we've tried to set deployment object manually, the operator itself changed the configuration back almost instantly.
Closing based on Dan's comment that wildcard routes are not yet supported but already have a jira tracking the RFE. https://jira.coreos.com/browse/PROD-1098
@Andy @Dan - the jira linked here no longer exists. I tried to find an matching one in the RFE project but didn't see one. The closest I saw here was https://issues.redhat.com/browse/NE-133 which stats that wildcard route is not included in the kube spec and the jira is closed as obsolete. There was a request for that to be documented. Can you confirm that a) we will not implement this and b) we have followed through on the documentation if that is the case Thank you
An option to enable wildcard routes was implemented in OpenShift 4.5. The feature was tracked in Jira as <https://issues.redhat.com/browse/NE-278>, and the corresponding enhancement proposal is <https://github.com/openshift/enhancements/blob/master/enhancements/ingress/wildcard-admission-policy.md>.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days