Skip to content
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

Jump to bottom

HPA: move from autoscaling v2beta1 to v2beta2 #721

Closed
zroubalik opened this issue Apr 2, 2020 · 2 comments
Closed

HPA: move from autoscaling v2beta1 to v2beta2 #721

zroubalik opened this issue Apr 2, 2020 · 2 comments
Assignees
@zroubalik
Labels
feature-request All issues for new features that have not been committed to
Milestone
v2.0

Comments

@zroubalik
Copy link
Member

zroubalik commented Apr 2, 2020 •
edited

We are using v2beta1 for our HPAs and scaling, we should consider moving to v2beta2. It shouldn't be a big change and cause any negative impact on KEDA functionality.

There are minor changes in the newer version of k8s autoscaling api, so we need to change our code appropriately.

https://stupefied-goodall-e282f7.netlify.com/contributors/design-proposals/autoscaling/hpa-v2/
@zroubalik zroubalik added the feature-request All issues for new features that have not been committed to label Apr 2, 2020
@zroubalik zroubalik added this to the v2.0 milestone Apr 2, 2020
@tomkerkhove
Copy link
Member

Sounds good to me!

@zroubalik zroubalik mentioned this issue Apr 8, 2020
Merged
@ahmelsayed
Copy link
Contributor

merged to v2 branch

@zroubalik zroubalik self-assigned this Apr 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@zroubalik zroubalik

Labels
feature-request All issues for new features that have not been committed to
Projects
None yet
Milestone
v2.0
Development

No branches or pull requests
3 participants
@ahmelsayed @zroubalik @tomkerkhove