"Customizing the web console URL" doesn't work. #724
Replies: 1 comment
-
Please don't create duplicate discussions on the same topic |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Below is the complete procedure for "Customizing the web console URL", ie accessing the Web Console from a different domain than the cluster's internal domain (which the cluster has been installed).
NOTE: This "extra" domain is normally used for external access to the cluster.
Customizing the web console URL
Customizing the web console URL
You can update the web console URL, consoleURL, to a custom value.
Procedure
Modify the cluster instance created by default during installation in the consoles.operator.openshift.io custom resource:
PROBLEM:
The above procedure is clearly insufficient to allow external access to the Web Console from a different domain ("external") URL.
We've done lots and lots of tests for over 12 hours and we always come up with a web page that says...
... when we try to access the Web Console from a different domain ("external") URL.
THE REAL CASE:
We can access the Web Console normally through the URL
https://console-openshift-console.apps.mbr.okd.local
which uses the domain okd.local with which the cluster has been installed.However if we try to access the "Web Console" from the new URL
https://console-openshift-console.apps.mbr.brlight.net
which uses the domain brlight.net the error Application is not available is reported on the web page.PROCEDURES PERFORMED:
Inform the new domain to be consumed by the Web Console...
Configure a new DNS zone (BIND 9) in the /etc/named/named.conf.local file...
... and in the /etc/named/zones/fw.brlight.net file...
The load balancer configuration (HAProxy) was kept as it was...
QUESTION: What was missing?
Thanks in advance! =D
Beta Was this translation helpful? Give feedback.
All reactions