We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When using the v0.7.1 helm chart for cse, we're getting the following error:
v0.7.1
error validating data: [ValidationError(HorizontalPodAutoscaler.spec.metrics[0].resource): unknown field "targetAverageUtilization" in io.k8s.api.autoscaling.v2beta2.ResourceMetricSource, ValidationError(HorizontalPodAutoscaler.spec.metrics[0].resource): missing required field "target" in io.k8s.api.autoscaling.v2beta2.ResourceMetricSource, ValidationError(HorizontalPodAutoscaler.spec.metrics[1].resource): unknown field "targetAverageUtilization" in io.k8s.api.autoscaling.v2beta2.ResourceMetricSource, ValidationError(HorizontalPodAutoscaler.spec.metrics[1].resource): missing required field "target" in io.k8s.api.autoscaling.v2beta2.ResourceMetricSource]
It looks like this change updated the API for HPA, but according to the Kubernetes HPA docs, it looks like the structure was changed from this:
metrics: - type: Resource resource: name: cpu targetAverageUtilization: 60
to this:
metrics: - type: Resource resource: name: cpu target: type: Utilization averageUtilization: 60
Here's another doc from Google GKE showing an example configuration supporting the new conventions.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
When using the
v0.7.1
helm chart for cse, we're getting the following error:It looks like this change updated the API for HPA, but according to the Kubernetes HPA docs, it looks like the structure was changed from this:
to this:
Here's another doc from Google GKE showing an example configuration supporting the new conventions.
The text was updated successfully, but these errors were encountered: