Closed ChristianGeie closed 1 year ago
Hi, if I understand it correctly, there is an error in the way metrics are builded.
{{- if .Values.autoscaling.targetCPUUtilizationPercentage }}
- type: Resource
resource:
name: cpu
targetAverageUtilization: {{ .Values.autoscaling.targetCPUUtilizationPercentage }}
{{- end }}
{{- if .Values.autoscaling.targetMemoryUtilizationPercentage }}
- type: Resource
resource:
name: memory
targetAverageUtilization: {{ .Values.autoscaling.targetMemoryUtilizationPercentage }}
when it should be sth like this:
type: Resource
resource:
name: cpu
target:
type: Utilization
averageUtilization: 60
I can try to fix it.
@tomrk-esteam8 yes please :)
@tomrk-esteam8 Do you want to simple switch to autoscaling/v2beta2
or do you want to use autoscaling/v2
furthermore and adapt the hpa template to it?
Please note that the api is only supported from v1.23 and the gcloud-sqlproxy helm chart will then become unusable for users who are still using an older kubernetes version.
@rimusz Are there any specifications as to which k8s version should be supported?
@ChristianGeie I would stick with autoscaling/v2
as it is already switched and chart is unusable anyway at this point.
@tomrk-esteam8 :+1:
Hello, in version
0.24.0
helmchart fails while applying hpa. For version0.23.0
everything works well.I see that between both version some changes regarding
apiVersion
happend, it was changed fromautoscaling/v2beta1
toautoscaling/v2
which is fine, because v2beta1 is deprecated in 1.19 and no longer served as of 1.25.autoscaling/v2
is available since 1.23, but has some breaking changes that are currently not reflected in the gcloud-sqlproxy chart.I would like to suggest using
autoscaling/v2beta2
to apply HorizontalPodAutoscaler ressource.K8s: v1.23.14-gke.1800 Error while applying helm chart: