-
Notifications
You must be signed in to change notification settings - Fork 1.8k
suggest OpenShift Online Pro router address #5815
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@jiri-fiala Thanks for your comments. |
Here are suggested router FQDNs for Pro clusters; one of these - depending on what cluster (US/EU/APAC) they are on - is where the CNAME DNS record of a user's custom domain should point to:
|
@wgordon17 @luciddreamz weren't we planning on implementing a way for users to get this information in the |
@tiwillia PR (https://github.com/openshift/online/pull/1465) is currently pending the release-ticket (https://github.com/openshift/online/issues/1466). The work on the release-ticket has not been performed yet from my understanding. Additionally, the master-config needs to be updated with the following information (https://docs.openshift.com/container-platform/3.6/install_config/router/default_haproxy_router.html#finding-router-hostname) to allow for helpful screens like openshift/origin-web-console#1194 |
@tiwillia I have created release-ticket (https://github.com/openshift/online/issues/1508) for adding router-canonical-hostname to paid cluster router's |
This is now config-managed for all of Online: https://github.com/openshift/online/issues/1508 |
Please mention explicitly how OpenShift Online Pro users can figure out their router FQDN for their cluster (i.e. using the
*.openshiftapps.com
URL when creating a default route) and/or list all the available Pro routers, somewhere here.This is needed for users to understand how exactly their DNS records are to be updated; the currently provided information "The OpenShift Online router’s domain is different for every cluster." is not sufficient.
Thank you.
The text was updated successfully, but these errors were encountered: