Hi.@Fabio: When you use the advanced setup you should set the `openshift_master_cluster_public_hostname` to `hosting.wfp.org`and rerun the install playbook.
I suggest to take a look into the now very detailed documentation. https://docs.openshift.org/latest/install_config/install/advanced_install.html#configuring-cluster-variables https://docs.openshift.org/latest/install_config/install/advanced_install.html#running-the-advanced-installation-system-container It's big but worth to read. ------ Originalnachricht ------ Von: "Joel Pearson" <[email protected]> An: "Fabio Martinelli" <[email protected]> Cc: [email protected] Gesendet: 03.01.2018 20:59:59 Betreff: Re: nginx in front of haproxy ?
It’s also worth mentioning that the console is not haproxy. That is the router, which run on the infrastructure nodes. The console/api server runs something else.The 'something else' is the openshift master server or the api servers depend on the setup.
Regards Aleks
On Wed, 3 Jan 2018 at 1:46 am, Fabio Martinelli <[email protected]> wrote:It was actually needed to rewrite the master-config.yaml in this other way, basically removing all the :8443 strings in the 'public' fields, i.e. to make it implicitly appear as :443[snipp]the strange PHP error message was due to another service listening on the 8443 port on the same host where nginx it's running !Exploiting this post https://github.com/openshift/origin/issues/17456 our nginx setup got now :upstream openshift-cluster-webconsole { ip_hash; server wfpromshap21.global.wfp.org:8443; server wfpromshap22.global.wfp.org:8443; server wfpromshap23.global.wfp.org:8443; } server { listen 10.11.40.99:80; server_name hosting.wfp.org; return 301 https://$server_name$request_uri; } server { listen 10.11.40.99:443; server_name hosting.wfp.org; access_log /var/log/nginx/hosting-console-access.log; #access_log off; error_log /var/log/nginx/hosting-console-error.log crit; include /data/nginx/includes.d/ssl-wfp.conf; include /data/nginx/includes.d/error.conf; include /data/nginx/includes.d/proxy.conf; proxy_set_header Host $host; location / { proxy_pass https://openshift-cluster-webconsole; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; } } and it seems to work by nicely masking the 3 Web Consoles. _______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
