-
Notifications
You must be signed in to change notification settings - Fork 432
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
Supporting HPA autoscaling/v2 #7634
Comments
I could probably add this in fairly quickly, but what fields are missing right now? Metrics and behaviour are both there and available to be defined from what I can see @pseudonator |
@kevin-shelaga yup both configs are supported but adding In addition IMO we should add a section in this docs page about this so people are aware if they are running in 1.23+ to specify |
@pseudonator my mistake i misread the template, i see it currently checks for v2beta for those fields. Makes sense now. |
Version
1.12.x (latest stable)
Is your feature request related to a problem? Please describe.
HPA has been graduated to GA and we should use autoscaling/v2 for all the HPAs that we create on Kubernetes v1.23+. This has been widely blogged as well.
This means that when Gloo is deployed with its current HPA on Kubernetes v1.23+, Kubernetes API will upgrade either
autoscaling/v1
orautoscaling/v2beta2
automatically toautoscaling/v2
. Downside to this is there currently isn't a good set of options to configure HPA forautoscaling/v2
version.Describe the solution you'd like
Gloo HPA configuration should include support for
autoscaling/v2
and various options.Describe alternatives you've considered
No response
Additional Context
Support matrix already includes Kubernetes 1.23 & 1.24 as supported.
The text was updated successfully, but these errors were encountered: