-
Notifications
You must be signed in to change notification settings - Fork 601
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
Bump HorizontalPodAutoscaler from deprecated v2beta2 to v2 #6332
Comments
/triage accepted |
@pierDipi: Please ensure the request meets the requirements listed here. If this request no longer meets these requirements, the label can be removed 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. |
/assign |
Hey @pierDipi, I think this needs to wait till after v1.6. Any way to move to that release? The minimum supported k8s version for v1.6 is still v1.22 and autoscaling/v2 isn't available in that k8s release. |
@gab-satchi Hi, are you still working on this issue ? if not, I would like to take it. |
Hi @liuchangyan, this needs to wait for a min k8s version bump due to #6424 (comment). This min k8s version bump is supposed to happen in 1.7 (today we are releasing 1.6), so we can start this after we have removed 1.22 from the KinD testing matrix and added 1.24 |
is this still open and available to be taken? |
Hi @amaanq, yes, this is available to be taken |
@amaanq still interested in this? Otherwise I will take it |
Problem
I'm getting this warning on k8s 1.23:
on
Persona:
Which persona is this feature for?
*
Exit Criteria
A measurable (binary) test that would indicate that the problem has been resolved.
Time Estimate (optional):
How many developer-days do you think this may take to resolve?
1
The text was updated successfully, but these errors were encountered: