Skip to content

Latest commit

 

History

History
21 lines (17 loc) · 1.66 KB

disconnected-ipv6-cluster-access.md

File metadata and controls

21 lines (17 loc) · 1.66 KB

Accessing a disconnected/ipv6 cluster deployed by Jetlag

Jetlag includes the installation of a HAProxy instance on the bastion machine with ipv6/disconnected environment setup. The HAProxy instance allows you to proxy traffic over ports 6443, 443, and 80 into the deployed disconnected cluster. Port 6443 is for access to the cluster api (Ex. oc cli commands), and ports 443/80 are for ingress routes such as console or grafana. This effectively allows you to reach the disconnected cluster from your local laptop. In order to do so you will need to edit your laptop's /etc/hosts and insert the routes that map to your cluster. While running the setup-bastion.yml playbook, an example copy of the hosts file is dumped into bastion_cluster_config_dir which is typically /root/bm for bare-metal cluster type.

Example:

$BASTION_IP api.bm.example.com
$BASTION_IP oauth-openshift.apps.bm.example.com
$BASTION_IP console-openshift-console.apps.bm.example.com
$BASTION_IP downloads-openshift-console.apps.bm.example.com
$BASTION_IP alertmanager-main-openshift-monitoring.apps.bm.example.com
$BASTION_IP grafana-openshift-monitoring.apps.bm.example.com
$BASTION_IP prometheus-k8s-openshift-monitoring.apps.bm.example.com
$BASTION_IP thanos-querier-openshift-monitoring.apps.bm.example.com
$BASTION_IP assisted-service-open-cluster-management.apps.bm.example.com
$BASTION_IP multicloud-console.apps.bm.example.com
$BASTION_IP dittybopper-dittybopper.apps.bm.example.com

$BASTION_IP should be the ip address that you can access the bastion from your laptop. If you create new routes you can always append them to your /etc/hosts file in order to reach any newly created routes.