Hide Forgot
+++ This bug was initially created as a clone of Bug #1347822 +++ Description of problem: As a user I want to use custom domain name for my application. That means I need to setup my DNS entry properly pointing at OpenShift routers. By default with some OpenShift configurations a "wildcard" dns name is used, and "default" routes are defined when I expose a service. With OpenShift v2 the ability to define an "alias", that pointed to this "default route" that was part of the "wildcard subdomain" was possible. With v3 this should again be made possible by allowing, the route object to define, multiple (acceptable) hostnames for the route (alternative name annotations). This would allow CNAMES (on dns providers) to point to the "default route" (hostname) and both DNS records would service request for the route. - Note: Conflicts should be resolved, in the same way route conflicts are resolved with routes today, first route wins, all others report an error, and the route is not accepted.
Could this not be accomplished with multiple routes?
(In reply to Dan McPherson from comment #2) > Could this not be accomplished with multiple routes? Yes, but I have a feeling that N routes for an application may case reload performance issues, greater than 1 route per application (with multiple names).
There shouldn't be a meaningful performance difference. I am more worried about this from a usability perspective. Namely, having two different ways to do the same thing (since you could always add two routes would still work). We would have to explain the difference (if there are any) between the two methods.