Skip to content

Commit

Permalink
bug 1613765 updating openshift_hostname information
Browse files Browse the repository at this point in the history
  • Loading branch information
kalexand-rh committed Oct 30, 2018
1 parent 60f1b39 commit 35a7f96
Show file tree
Hide file tree
Showing 2 changed files with 15 additions and 8 deletions.
21 changes: 14 additions & 7 deletions install/prerequisites.adoc
Expand Up @@ -397,9 +397,8 @@ the router will be deployed:
*.cloudapps.example.com. 300 IN A 192.168.133.2
----

In almost all cases, when referencing VMs you must use host names, and the host
names that you use must match the output of the `hostname -f` command on each
node.
When referencing VMs, use the host names that the output of the `hostname -f`
command on each node.

[WARNING]
====
Expand Down Expand Up @@ -632,9 +631,17 @@ connections, and is only required if you have clustered etcd.
*Notes*

* In the above examples, port *4789* is used for User Datagram Protocol (UDP).
* When deployments are using the SDN, the pod network is accessed via a service proxy, unless it is accessing the registry from the same node the registry is deployed on.
* {product-title} internal DNS cannot be received over SDN. For non-cloud deployments, this will default to the IP address associated with the default route on the master host. For cloud deployments, it will default to the IP address associated with the first internal interface as defined by the cloud metadata.
* The master host uses port *10250* to reach the nodes and does not go over SDN. It depends on the target host of the deployment and uses the computed value of `*openshift_public_hostname*`.
* When deployments are using the SDN, the pod network is accessed via a service
proxy, unless it is accessing the registry from the same node the registry is
deployed on.
* {product-title} internal DNS cannot be received over SDN. For non-cloud
deployments, this will default to the IP address associated with the default
route on the master host. For cloud deployments, it will default to the IP
address associated with the first internal interface as defined by the cloud
metadata.
* The master host uses port *10250* to reach the nodes and does not go over SDN.
It depends on the target host of the deployment and uses the computed value of
`*openshift_public_hostname*`.
* Port *1936* can still be inaccessible due to your iptables rules. Use the following to configure iptables to open port *1936*:
+
----
Expand Down Expand Up @@ -725,7 +732,7 @@ topic discusses the available Ansible variables in greater detail.
|Variable |Usage

|`*hostname*`
a| - Resolves to the internal IP from the instances themselves.
a| - Resolves to the internal IP address from the instances themselves.

|`*ip*`
a| - The internal IP address of the instance.
Expand Down
2 changes: 1 addition & 1 deletion release_notes/ocp_3_10_release_notes.adoc
Expand Up @@ -1036,7 +1036,7 @@ previously be set via `openshift_dns_ip`.

[discrete]
[[ocp-310-deprecated-openshift_hostname]]
=== Deprecated openshift_hostname Variable
=== Removed openshift_hostname Variable

The `openshift_hostname` variable is now removed.

Expand Down

0 comments on commit 35a7f96

Please sign in to comment.