Skip to content
This repository has been archived by the owner on Dec 8, 2023. It is now read-only.

introduce the system-upgrade-controller #353

Merged
merged 1 commit into from
Jan 17, 2020

Conversation

dweomer
Copy link
Contributor

@dweomer dweomer commented Jan 16, 2020

See https://github.com/rancher/system-upgrade-controller

also:

  • fixes broken ldd with alpine 3.11
  • bumps k3s to v1.17.0+k3s.1

- fixes broken ldd with alpine 3.11
- bumps k3s to v1.17.0+k3s.1
@dweomer
Copy link
Contributor Author

dweomer commented Jan 16, 2020

Supersedes #284

@dweomer dweomer merged commit f118f95 into rancher:master Jan 17, 2020
@dweomer dweomer deleted the system-upgrade-controller branch January 17, 2020 17:02
@dweomer dweomer added this to the v0.9.0 milestone Jan 17, 2020
@dweomer dweomer mentioned this pull request Jan 28, 2020
4 tasks
@blaggacao
Copy link

Maybe this question could be preemptively answered in the docs:

Since https://rancher.com/docs/k3s/latest/en/upgrades/automated/ promotes a phased approach preferring master nodes over agent nodes, yet this very PR does not make a distinction, a thought process must have been made over whether the upgrade order is essentially irrelevant or whether master nodes shall be preferred, in which you came to the former conclusion.

The question is: Why? (What are the arguments and conclusions? - it might not be easy to infer, for a layman and at the same time be guaranteed to be educational)

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

Successfully merging this pull request may close these issues.

2 participants