Shubham

Hi, AFAIK It's strongly recommended to keep the minor version of the Cluster Autoscaler matching the version of the k8s cluster it's deployed to give the strong coupling of the...

/cc @gjtempleton

> @Shubham82 I understand that recommendation but if, for example, I am going to upgrade my cluster from 1.20 to 1.21 I need to do one of two things: >...

Hi, @gjtempleton Could please take a look?

Hi @zalmarge IMO the cloud provider cherry server was added after the CA v1.24.0 branch cut and not present in the /cluster-autoscaler-release-1.24 branch: https://github.com/kubernetes/autoscaler/tree/cluster-autoscaler-release-1.24/cluster-autoscaler/cloudprovider/builder It is present in the master...

Hi @gjtempleton @MaciekPytel am I going right? WDYT? Should we remove this thing from [release notes](https://github.com/kubernetes/autoscaler/releases?q=24&expanded=true)?

@zalmarge you can make an image or build the code (from the master branch) by using [Makefile](https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/Makefile). There is a `make-image` rule which builds the image for CA(master). The following...

thanks @gjtempleton

Hi @zalmarge JFYI: CherryServer has been removed from Cluster Autoscaler 1.24.0 [release notes](https://github.com/kubernetes/autoscaler/releases?q=24&expanded=true).

Hi, It is because the `user` flag which is mentioned here is shadowed by a global flag. See this comment: https://github.com/kubernetes/kubernetes/pull/108654#issuecomment-1082504900 PR opened for it in past but has not...