Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrading Nodes Manually #3740

Open
ShunsukeMiyake opened this issue Nov 8, 2024 · 0 comments
Open

Upgrading Nodes Manually #3740

ShunsukeMiyake opened this issue Nov 8, 2024 · 0 comments

Comments

@ShunsukeMiyake
Copy link

ShunsukeMiyake commented Nov 8, 2024

I would like to know more about "Upgrading Nodes Manually" as described in the following document: https://rke.docs.rancher.com/upgrades#upgrading-nodes-manually

We are considering upgrading the Kubernetes version of our downstream cluster.
Could you advise on how we could initiate the upgrade to manually upgrade each node one at a time?

Our company uses Rancher to manage our clusters.
Since the target cluster for the upgrade was set up using Rancher's UI, we have access to the configuration (cluster.yaml) via the Rancher UI.
If we change the Kubernetes version in this configuration, the upgrade for each node would likely start automatically.

However, since we would like to upgrade each node manually, we are thinking of setting the following options as shown below.
Would this allow us to perform each node's upgrade manually?

  • Drain nodes -> false
  • Maximum Worker Nodes Unavailable -> 0

For example, within the cluster, we have Redis, with the master and slave located on separate nodes.
When the master begins upgrading, I believe it will take a certain amount of time for the slave to detect that it can no longer communicate with the master.
During this period, data cannot be recorded to the master, leading to a potential data loss for that time span.
To minimize data loss, we would like to control the order and timing of the upgrade—for instance, by starting the upgrade from the slave.

Thank you for reading.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant