Document URL: https://docs.openshift.com/container-platform/4.2/networking/ingress-operator.html#nw-ingress-sharding-route-labels_configuring-ingress Describe the issue: By default, route is exposed to both routers (internal and external) Perhaps documentation should reflect this. Suggestions for improvement: Reference link to apply routeSelector to default router. https://rcarrata.com/openshift/ocp4_route_sharding/
So this from the link: "By default, the default router have not routeSelector (remember the spec:{} from above?), and for this reason is exposed not only to our internal router, also is exposed to the default." And if that isn't desirable, then: "For ONLY expose the routes of *.internalapps to one router (the internal router), and avoid to the default router (that expose the *.apps routes normally), a routeSelector must be defined into the ingresscontroller “default” in the namespace of openshift-ingress-operator:" So is the use of `routeSelector` what makes this feature "route sharding"? Thanks.
Hi Brandi, Can you take a look at this? Thanks!
Hey Jason, I'll take this one on. Thanks!
@bmcelvee - please provide an update on this item. Thanks!
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days