Custom metrics adapter spewing errors "apiserver was unable to write a fallback JSON response: http2: stream closed" about k8s-stackdriver HOT 11 OPEN

@red8888 I had the same issue, I had to deploy adapter_new_resource_model.yaml because I wanted to use external metrics but in this file along with v1beta1.external.metrics.k8s.io service you also get v1beta1.custom.metrics.k8s.io and v1beta2.custom.metrics.k8s.io.

Since I didn't use any custom metrics in the cluster so I just removed v1beta1.custom.metrics.k8s.io and v1beta2.custom.metrics.k8s.io APIServices and now I don't get these logs (this obviously won't work if you need custom metrics for scaling)

from k8s-stackdriver.

Ran into this as well. Any advice on a solution would be welcome. our Pubsub autoscalers stopped functioning and we can't tell if this message is causational or correlational

from k8s-stackdriver.

I have the same issue, any solutions?

from k8s-stackdriver.

I have the same issue on GKE 1.25+

from k8s-stackdriver.

@red8888 Did you find any solution for this ?

from k8s-stackdriver.

FWIW I was able to work around this in the same way @5imun did -- I removed the APIService registrations for custom metrics. But this is obviously not a great solution. :(

from k8s-stackdriver.

Same issue - cant use custom metrics for hpa autoscaling in GKE because of this.

from k8s-stackdriver.

Same issue here: #318

from k8s-stackdriver.

We have the same issue. Fortunately we wanted Pubsub-based autoscaling so that is an external-metric, so the solution that @5imun suggested worked for us.

from k8s-stackdriver.

should be a good idea to understand why we have those message

from k8s-stackdriver.

Update: this PR only fixes OOM and this spam log has not been fixed.

Hi, could you try v0.14.2? It contains the fix #623

from k8s-stackdriver.