public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-04-29 01:33:12 +00:00
Code Issues Packages Projects Releases Wiki Activity

adds note for node-drain behavior

Browse Source
This commit is contained in:
Apoorva Jagtap
2026-02-06 12:14:50 +05:30
parent 20fab76cfc
commit 0ee6a3b95a
3 changed files with 21 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
versioned_docs/version-2.13/getting-started/installation-and-upgrade/upgrade-and-roll-back-kubernetes.md
+7
View File
@@ -100,6 +100,13 @@ There is a [known issue](https://github.com/rancher/rancher/issues/25478) in whi
:::
:::note
During an upgrade, nodes may be drained even when no user-visible YAML changes are present. This can occur if non-dynamic configuration files are updated or if a new `system-agent-installer` image is introduced.
In such cases, Rancher generates a new upgrade plan, resulting in a new plan hash. When `Upgrade Strategy` is set to `Drain nodes`, this plan change can trigger node draining.
:::
### Maintaining Availability for Applications During Upgrades
In [this section of the RKE documentation,](https://rancher.com/docs/rke/latest/en/upgrades/maintaining-availability/) you'll learn the requirements to prevent downtime for your applications when upgrading the cluster.