Questions about upgrading cluster-autoscaler from 1.23 to 1.28

kubernetes / autoscaler

Autoscaling components for Kubernetes

Apache License 2.0

8.1k stars 3.98k forks source link

Questions about upgrading cluster-autoscaler from 1.23 to 1.28 #6972

Open duyawen8 opened 5 months ago

duyawen8 commented 5 months ago

Which component are you using?: cluster-autoscaler

Is your feature request designed to solve a problem? If so describe the problem this feature should solve.:

Describe the solution you'd like.:

Describe any alternative solutions you've considered.:

Additional context.:

I want to upgrade CA from 1.23 to 1.28 to use the parallel drain feature. The kubernetes version is 1.21. Is there any compatibility issue?

Shubham82 commented 5 months ago

Hi @duyawen8, there will be a compatibility issue, if you use k8s v1.21 for CA 1.28. For CA 1.28, you have to use k8s v1.28. See the release section under README.md for the corresponding k8s version to the CA version.

Shubham82 commented 5 months ago

/remove-kind feature /kind support

adrianmoisey commented 5 months ago

/area cluster-autoscaler

Shubham82 commented 4 months ago

@duyawen8, if your concern is resolved so can we close this issue?

duyawen8 commented 4 months ago

I know that the CA version and the kubernetes version have a one-to-one correspondence. Is there any way to use CA 1.28 for parallel eviction without upgrading the cluster? Are there definitely compatibility issues?

Shubham82 commented 4 months ago

IMO there will be compatibility issues because For every CA release, we update corresponding upstream dependencies(k8s). so there might be issues with mismatched and deprecated API items, I don't think it's recommended to use a CA that is greater than your cluster version.

Shubham82 commented 4 months ago

cc @gjtempleton @MaciekPytel your thoughts on this?

k8s-triage-robot commented 1 month 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:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle stale
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

Shubham82 commented 1 month ago

IMO there will be compatibility issues because For every CA release, we update corresponding upstream dependencies(k8s). so there might be issues with mismatched and deprecated API items, I don't think it's recommended to use a CA that is greater than your cluster version.

cc @MaciekPytel @gjtempleton @jackfrancis WDYT?

Shubham82 commented 1 month ago

/remove-lifecycle stale