-
Notifications
You must be signed in to change notification settings - Fork 49
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
Support InPlace
upgrade for worker machines
#792
Comments
The issue is marked as stale since no activity has been recorded in 30 days |
Dear k0smotron team, can you please share the plan on getting this fixed? This issue was opened some time ago and in general it's important for the k0rdent project experience. (cc @mestadler @p5ntangle fyi folks) |
First of all, fix is the wrong word as this is a new feature, not a bug. I'm not entirely sure if k0smotron can even "fix" this. The worker From CAPI/k0rdent point of view, how would you want this to work? I.e. what are the expected steps to trigger worker |
From the k0rdent perspective, it would be great to have the same approach we currently use for the With the I understand that implementing this in k0smotron may be difficult or even impossible, but I wanted to bring it up for discussion (just in case). |
The main challenge is that We can keep this still around if we come up with any idea how this could be done, but currently it seems pretty impossible to implement.
|
Currently, according to k0smotron docs, the
InPlace
upgrade (using autopilot) is supported for control plane machines only: https://docs.k0smotron.io/stable/update/update-capi-cluster/. It'll be good to support the same approach for worker machines as well if possible.The text was updated successfully, but these errors were encountered: