Bug 1650698, updated RHEL support information

install/host_preparation.adoc

@@ -21,7 +21,7 @@ ifdef::openshift-enterprise[]
 == Operating system requirements
 
 Master and node hosts must use a base installation of Red Hat Enterprise Linux
-(RHEL) 7.4 or 7.5 with the latest packages from the Extras
+(RHEL) 7.4 or later with the latest packages from the Extras
 channel or RHEL Atomic Host 7.4.2 or later. See the following documentation for
 the respective installation instructions, if required:
 

install/prerequisites.adoc

@@ -44,15 +44,15 @@ The system requirements vary per host type:
 a|- Physical or virtual system or an instance running on a public or private IaaS.
 ifdef::openshift-origin[]
 - Base OS: Fedora 21, CentOS 7.4,
-link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html-single/installation_guide/index[Red Hat Enterprise Linux (RHEL) 7.4 or 7.5]
+link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html-single/installation_guide/index[Red Hat Enterprise Linux (RHEL) 7.4 or later]
 with the "Minimal" installation option and the latest packages from the Extras
 channel, or
 link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux_atomic_host/7/html-single/installation_and_configuration_guide/[RHEL Atomic Host]
 7.4.5 or later.
 endif::[]
 ifdef::openshift-enterprise[]
 - Base OS:
-link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html-single/installation_guide/index[Red Hat Enterprise Linux (RHEL) 7.4 or 7.5]
+link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html-single/installation_guide/index[Red Hat Enterprise Linux (RHEL) 7.4 or later]
 with the "Minimal" installation option and the latest packages from the Extras
 channel, or
 link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux_atomic_host/7/html-single/installation_and_configuration_guide/[RHEL Atomic Host]
@@ -70,14 +70,14 @@ temporary directory. image:redcircle-2.png[]
 a| * Physical or virtual system, or an instance running on a public or private IaaS.
 ifdef::openshift-origin[]
 * Base OS: Fedora 21, CentOS 7.4,
-link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html-single/installation_guide/index[RHEL 7.4 or 7.5]
+link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html-single/installation_guide/index[RHEL 7.4 or later]
 with "Minimal" installation option, or
 link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux_atomic_host/7/html-single/installation_and_configuration_guide/[RHEL Atomic Host]
 7.4.5 or later.
 endif::[]
 ifdef::openshift-enterprise[]
 * Base OS:
-link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html-single/installation_guide/index[RHEL 7.4 or 7.5]
+link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html-single/installation_guide/index[RHEL 7.4 or later]
 with "Minimal" installation option, or
 link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux_atomic_host/7/html-single/installation_and_configuration_guide/[RHEL Atomic Host]
 7.4.5 or later.
@@ -455,7 +455,7 @@ domain is not listed in the search list. Otherwise, containers managed by
 
 When you set up a cluster that is not integrated with a cloud provider, you must
 correctly set your nodes' host names. Each node's host name must be resolvable,
-and each node must be able to reach each other node. 
+and each node must be able to reach each other node.
 
 To confirm that a node can reach another node:
 
@@ -711,10 +711,10 @@ 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 
+* 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 
+* {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