This message was deleted.
# helpdesk
s
This message was deleted.
c
Which version of egress? All but the one released on Monday have an issue with cpu load computation that could explain this. Hard to tell if it's the issue though. A look at the individual metrics returned by each pod may help
r
Version 1.4.2
c
This version could have that issue, depending on the environment where the pod runs. What does the cpu metric exported by the egress service say for all instances??
r
I’m using the custom metric livekit_egress_available there is another thread where I ask exactly how to use this with hpa in K8s
So far no workable solution has been given
c
Again, what do you get for the other exported metrics? livekit-node-cpu_load particularly
r
I will check I was particularly concerned with egress but let me get back to you
I see the following
kubectl get --raw “/apis/custom.metrics.k8s.io/v1beta1/namespaces/default/pods/*/livekit_node_cpu_load” | jq . { “kind”: “MetricValueList”, “apiVersion”: “custom.metrics.k8s.io/v1beta1”, “metadata”: {}, “items”: [ { “describedObject”: { “kind”: “Pod”, “namespace”: “default”, “name”: “livekit-egress-766c4c54f-s9jtk”, “apiVersion”: “/v1" }, “metricName”: “livekit_node_cpu_load”, “timestamp”: “2022-10-28T005738Z”, “value”: “27m”, “selector”: null }, { “describedObject”: { “kind”: “Pod”, “namespace”: “default”, “name”: “livekit-egress-766c4c54f-v2qvt”, “apiVersion”: “/v1" }, “metricName”: “livekit_node_cpu_load”, “timestamp”: “2022-10-28T005738Z”, “value”: “5m”, “selector”: null } ] }
Anyway I may of solved my problem in another way. Thanks for the assistance