-
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
Cherry pick #4394 onto release v1.19.2 #4732
Comments
Hi there, we can't cherry-pick this onto an existing release, however, we've cut releases out of our usual support windows to address issues like this before. I've added discussing cutting a 1.19.3 release to include this fix to the agenda for the next SIG meeting. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
A 1.19.3 release has been cut. |
@gjtempleton: 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. |
Which component are you using?:
cluster-autoscaler
What version of the component are you using?:
v1.19.2
What environment is this in?:
EKS v1.19
What did you expect to happen?:
Fix on #4394 should be available.
What happened instead?:
The bug still exists.
How to reproduce it (as minimally and precisely as possible):
This was already described here #4389 and merged here #4394.
Anything else we need to know?:
This is a request to cherry pick this change to 1.19.2.
The text was updated successfully, but these errors were encountered: