-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Magnum][ClusterAutoscaler] Backport control-plane label #5888
Comments
IMO, we can do the cherry-picked #5776 to the previous releases. @tghartland, what are your thoughts on this? |
We can do it in the following release of CA: 1.26, 1.25, 1.24 |
No reason it can't be backported. |
Thanks @tghartland for the above info. |
That would be amazing! ^^ |
@modzilla99 as per @tghartland above comment, it can't backport. |
It can be backported. Sorry if I worded it confusingly! |
@tghartland Please don't be sorry and thanks for confirmation. |
/assign |
I checked it, we have to do it for CA v1.27 also because it is not there: https://github.com/kubernetes/autoscaler/blob/cluster-autoscaler-release-1.27/cluster-autoscaler/cloudprovider/magnum/magnum_cloud_provider.go These changes will reflect in the CA v1.28, so i will backport it in the v1.27 also. |
@tghartland and @modzilla99 |
lgtm |
All good. |
Thanks @tghartland and @modzilla99 for taking a look at PRs. |
/close |
@Shubham82: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Thank you @Shubham82 ! |
I fixed #5751 with #5776, but since we already deploy v1.26 and v1.27 with that node role, those versions are also effected. Can this change be cherry-picked for those releases as well, or do we have to build custom images for our customers?
The text was updated successfully, but these errors were encountered: