From e7b1186d567efb588ff1948f5e189fc497ff0b14 Mon Sep 17 00:00:00 2001 From: Denise Date: Wed, 5 Sep 2018 21:53:15 -0700 Subject: [PATCH] Update _index.md --- .../rancher/v2.x/en/installation/ha/kubernetes-rke/_index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/rancher/v2.x/en/installation/ha/kubernetes-rke/_index.md b/content/rancher/v2.x/en/installation/ha/kubernetes-rke/_index.md index 4234c2e9656..55eaadac4d6 100644 --- a/content/rancher/v2.x/en/installation/ha/kubernetes-rke/_index.md +++ b/content/rancher/v2.x/en/installation/ha/kubernetes-rke/_index.md @@ -9,7 +9,7 @@ Use RKE to install Kubernetes with a high-availability etcd configuration. Using the sample below create the `rancher-cluster.yml` file. Replace the IP Addresses in the `nodes` list with the IP address or DNS names of the 3 Nodes you created. -> **Note:** If you node has public and internal addresses, its recommended to set `internal_address:` so Kubernetes will use it for intra-cluster communication. Some services like AWS EC2 require setting `internal_address:` if you want to use self-referencing security groups or firewalls. +> **Note:** If your node has public and internal addresses, it is recommended to set the `internal_address:` so Kubernetes will use it for intra-cluster communication. Some services like AWS EC2 require setting the `internal_address:` if you want to use self-referencing security groups or firewalls. ```yaml nodes: @@ -107,4 +107,4 @@ Save a copy of the `kube_config_rancher-cluster.yml` and `rancher-cluster.yml` f See the [Troubleshooting]({{< baseurl >}}/rancher/v2.x/en/installation/ha/kubernetes-rke/troubleshooting/) page. -### [Next: Initialize Helm]({{< baseurl >}}/rancher/v2.x/en/installation/ha/helm-init/) \ No newline at end of file +### [Next: Initialize Helm]({{< baseurl >}}/rancher/v2.x/en/installation/ha/helm-init/)