Naveenkumar K

I'm also facing the same issue. I am using ubuntu 20.0 and ROS Neotic. is the problem due to using new versions? I can follow everything other than mavros, mavros_msgs,mavlink...

Thanks @lizardruss for your reply. Yeah, the example you gave is helping, I can implement my use case with the help of that. My suggestion would be instead of read,...

Hi @mikkeloscar, thanks for the explanation. When the Prometheus query is modified to return zero if the metric is unavailable fixes the issue. Now one thing I want to understand...

Hi @mikkeloscar , I just wanted some clarification. After the Prometheus query is modified as you mentioned the issue is solved. As the two metrics will always have definite values,...

Hi @mikkeloscar , Thanks for the quick reply! Do you want kube-metrics-adapter logs in the issue timeframe alone or do you also want logs before and after a specific hour...

Hi @mikkeloscar , I reproduced the issue as mentioned in the description, this time the sla-metric value stuck at **375m/ 500**. But when I queried on Prometheus, it showed a...

Hi @mikkeloscar sure Still the hpa is showing random value , but actual value is zero only. kubectl describe hpa ``` Name: pod-name-hpa Namespace: my-namespace Labels: app.kubernetes.io/managed-by=Helm Annotations: meta.helm.sh/release-name: pod-name...

Thanks for the support @mikkeloscar. We are currently using Kube version **v1.24.7**. I am also not able to find the relevant issues in the Kubernetes project. Anyway, I have already...

Thanks @brendandburns and @liggitt I want to add some more context, we had enabled the debug level and got the token from the response header. When I tried to decode...