Open jnlycklama opened 3 months ago
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The compatibility matrix is imprecise on how to handle upgrades https://github.com/kubernetes/client-go/?tab=readme-ov-file#compatibility-matrix.
The chart tells us each client version will only be 100% compatible with the same AKS version. If that is true, how should cluster upgrades be handled? The C# SDK supports n-2 versions https://github.com/kubernetes-client/csharp#version-compatibility which allows for more leeway