+
+services:
+ etcd:
+ snapshot: true
+ creation: 6h
+ retention: 24h
+
+# Remove addons section from here til end of file
+addons: |-
+ ---
+ ...
+# End of file
+```
+
### Follow Helm and Rancher install steps
From here follow the standard install steps.
diff --git a/content/rke/v0.1.x/en/config-options/cloud-providers/vsphere/_index.md b/content/rke/v0.1.x/en/config-options/cloud-providers/vsphere/_index.md
index 80169afd0b7..fdfdddcac7c 100644
--- a/content/rke/v0.1.x/en/config-options/cloud-providers/vsphere/_index.md
+++ b/content/rke/v0.1.x/en/config-options/cloud-providers/vsphere/_index.md
@@ -58,7 +58,7 @@ The vSphere configuration options are divided into 5 groups:
### global
-The main purpose of global options is to be able to define a common set of configuration parameters that will be inherited by all vCenters defined under the `virtual_center` directive unless explicitely defined there.
+The main purpose of global options is to be able to define a common set of configuration parameters that will be inherited by all vCenters defined under the `virtual_center` directive unless explicitly defined there.
Accordingly, the `global` directive accepts the same configuration options that are available under the `virtual_center` directive. Additionally it accepts a single parameter that can only be specified here:
diff --git a/layouts/shortcodes/requirements_ports_rke.html b/layouts/shortcodes/requirements_ports_rke.html
index 01b76d194fc..c972bed77d2 100644
--- a/layouts/shortcodes/requirements_ports_rke.html
+++ b/layouts/shortcodes/requirements_ports_rke.html
@@ -304,6 +304,6 @@
Information on local node traffic
- Kubernetes healthchecks (livenessProbe and readinessProbe) are executed on the host itself. On most nodes, this is allowed by default. When you have applied strict host firewall (i.e. iptables) policies on the node, or when you are using nodes that have multiple interfaces (multihomed), this traffic gets blocked. In this case, you have to explicitely allow this traffic in your host firewall, or in case of public/private cloud hosted machines (i.e. AWS or OpenStack), in your security group configuration. Keep in mind that when using a security group as Source or Destination in your security group, that this only applies to the private interface of the nodes/instances.
+
Kubernetes healthchecks (livenessProbe and readinessProbe) are executed on the host itself. On most nodes, this is allowed by default. When you have applied strict host firewall (i.e. iptables) policies on the node, or when you are using nodes that have multiple interfaces (multihomed), this traffic gets blocked. In this case, you have to explicitly allow this traffic in your host firewall, or in case of public/private cloud hosted machines (i.e. AWS or OpenStack), in your security group configuration. Keep in mind that when using a security group as Source or Destination in your security group, that this only applies to the private interface of the nodes/instances.
diff --git a/scripts/build-algolia.js b/scripts/build-algolia.js
index ebbf2fb4b5f..efc80f581d3 100755
--- a/scripts/build-algolia.js
+++ b/scripts/build-algolia.js
@@ -79,7 +79,7 @@ nodes.forEach(node => {
}
- // remove potentially large content (see size limits) and replace with teh summary so that we don't get results with zero highlightable results
+ // remove potentially large content (see size limits) and replace with the summary so that we don't get results with zero highlightable results
node.content = node.summary;
// remove summary for dedup
diff --git a/scripts/dev b/scripts/dev
index 3ede772eac6..b75c0331226 100755
--- a/scripts/dev
+++ b/scripts/dev
@@ -63,7 +63,7 @@ while getopts ":bdp:t:u" opt;do
UPLOAD="true"
;;
\?)
- echoerr "Invalid arguemnts"
+ echoerr "Invalid arguments"
print_help
exit 1
;;
diff --git a/src/img/rancher/horizontal-pod-autoscaler.jpg b/src/img/rancher/horizontal-pod-autoscaler.jpg
new file mode 100644
index 00000000000..e39eae1bff8
Binary files /dev/null and b/src/img/rancher/horizontal-pod-autoscaler.jpg differ