public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-26 04:58:07 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix How Upgrades Work link to cluster.yaml

Browse Source
This commit is contained in:
Terdunov Vyacheslav
2020-04-01 13:58:04 +04:00
committed by GitHub
parent b96fb448ea
commit 7eb1c17dd1
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rke/latest/en/upgrades/how-upgrades-work/_index.md
+2 -2
View File
@@ -62,7 +62,7 @@ Because RKE addons are necessary for allowing traffic into the cluster, they wil
For more information on configuring the number of replicas for each addon, refer to [this section.](#replicas-for-rke-addons)
For an example showing how to configure the addons, refer to the [example cluster.yml.](#example-cluster-yml)
For an example showing how to configure the addons, refer to the [example cluster.yml.]({{<baseurl>}}rke/latest/en/upgrades/configuring-strategy/#example-cluster-yml)
{{% /tab %}}
{{% tab "RKE prior to v1.1.0" %}}
@@ -87,4 +87,4 @@ Worker nodes are upgraded simultaneously, in batches of either 50 or the total n
When a worker node is upgraded, it restarts several Docker processes, including the `kubelet` and `kube-proxy`. When `kube-proxy` comes up, it flushes `iptables`. When this happens, pods on this node can’t be accessed, resulting in downtime for the applications.
{{% /tab %}}
{{% /tabs %}}
{{% /tabs %}}