Skip to content

jmarley/openshift-console-on-port-443

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

3 Commits
 
 
 
 

Repository files navigation

Reroute OpenShift Console to port 443

The purpose of this is to expose the console on different port than the default 8443. There are ways to expose the console natively from master on 443, but from what I understand there can be quite a number of tricky things that happen when it is manually altered, thus we are going to try and expose as an Endpoint.

Prerequisites

  1. OSE master ip address: <ose-master-ip>

  2. OSE master hostname: <ose-master-hostname>

  3. OSE console host domain: <new-ose-console-domain>

Note
The new console domain can be whatever you want on top of the subdomain. It just has to be routable to node hosting haproxy.
Create Service layer
$ oc create -f openshift/service.yaml
Create Endpoint layer
$ sed -i 's/<template-master-ip-address>/<ose-master-ip>/g' \
openshift/service.yaml
$ oc create -f openshift/endpoint.yaml
Create routing layer
$ sed -i 's/<template-ose-console-domain>/<new-ose-console-domain>:443/g' \
openshift/route.yaml
$ oc create -f openshift/route.yaml
Edit master configuration
$ sed -i 's/https://<ose-master-hostname>:8443/<new-ose-console-domain>:443/g' \
/etc/origin/master/master-config.yaml
Restart master
$ systemctl restart atomic-openshift-master

About

The purpose of this is to expose the console on different port than the default 8443, specifically 443.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published