Use InternalApi network for openshift_master_cluster_hostname

According to the inventory examples[1] openshift_master_cluster_hostname
points to an internal hostname/address set on the loadbalancer while
openshift_master_cluster_public_hostname points to the external.
This change sets openshift_master_cluster_hostname to use the InternalApi
network instead of the External network as it is at this moment.

[1] https://docs.openshift.com/container-platform/3.11/install/example_inventories.html

Change-Id: I9efab5b07682efd6b03da433801d636e7d324619
(cherry picked from commit bd51cf5f44)
This commit is contained in:
Marius Cornea 2018-11-30 13:25:03 -05:00 committed by Martin André
parent 21b016cfb1
commit 0df3b82da8
1 changed files with 1 additions and 1 deletions

View File

@ -200,7 +200,7 @@ outputs:
tripleo_stack_action: {get_param: StackAction}
openshift_master_node_vars: {get_param: OpenShiftMasterNodeVars}
openshift_master_cluster_vars:
openshift_master_cluster_hostname: {get_param: [EndpointMap, OpenshiftPublic, host]}
openshift_master_cluster_hostname: {get_param: [EndpointMap, OpenshiftInternal, host]}
openshift_master_cluster_public_hostname: {get_param: [EndpointMap, OpenshiftPublic, host]}
# NOTE(flaper87): Check if origin-node is running in the openshift