antonin-a
commented
6 days ago Hello @Lodeis,
Rolling back a Kubernetes version in a managed environment, like the one OVHcloud provides, is not advisable due to several critical risks. First, Kubernetes upgrades often introduce changes that aren’t reversible, particularly in areas like API compatibility, storage, and resource management. Reverting to an older version could lead to data corruption, deployments incompatibility with newer components, and cluster instability.
The Kubernetes community itself does not support rollbacks, emphasizing the risk of unpredictable behavior and breakage across the cluster’s components. Instead, best practices in production environments suggest testing new versions in staging before upgrading, to ensure all your tools, like Velero, are fully compatible. If not possible, a safer approach is to delay upgrading your production cluster until third-party tools have been updated to work with the latest version (we support 3 Kubernetes versions giving a support windows of approx. 12 months). This avoids the risks and complexities associated with rolling back, while still keeping your environment secure and stable.
As an OVHcloud customer using Managed Kubernetes Service, I want to be able to rollback my kubernetes cluster version. So that in case a kubernetes specific tool such as Velero doesn't work on the upgraded cluster (despite velero being up to date), I can return to the previous version of the cluster to make it work again and wait for a Velero version that work on the next kubernetes version.
I believe it is an important feature for a production environment.