You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've already looked into this, but I haven't been able to fully understand the current state.
We are using:
Kubeadm Bootstrap Provider
Kubeadm Control Plane Provider
OpenStack Infrastructure Provider
With the latest versions of CAPI and these providers + InPlaceUpdates feature flag enabled in CAPI, are the following operations supported for both control plane and worker nodes already?
In-place Kubernetes version upgrades (for example, from 1.34 to 1.35)
In-place flavor changes (CPU, memory, root disk)
If not, what is missing, and where would the necessary changes need to be implemented (e.g., Cluster API core, KCP, or the infrastructure provider)?
Our primary use case is to improve support for running larger database clusters on Kubernetes with local storage, where minimizing node replacements is essential to avoid frequent re-syncs (e.g. Galera or PostgreSQL clusters).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I've already looked into this, but I haven't been able to fully understand the current state.
We are using:
With the latest versions of CAPI and these providers + InPlaceUpdates feature flag enabled in CAPI, are the following operations supported for both control plane and worker nodes already?
If not, what is missing, and where would the necessary changes need to be implemented (e.g., Cluster API core, KCP, or the infrastructure provider)?
Our primary use case is to improve support for running larger database clusters on Kubernetes with local storage, where minimizing node replacements is essential to avoid frequent re-syncs (e.g. Galera or PostgreSQL clusters).
Thank you!
Beta Was this translation helpful? Give feedback.
All reactions