Live data from Hacker News

Kubernetes horizontal pod autoscaling powered by an OpenTelemetry-native tool

dash0.com

1–7 of 7 posts

Re: Kubernetes horizontal pod autoscaling powered by an OpenTelemetry-native tool

#3
While useful, this is a more fragile autoscaling solution that HPA out of the box. It requires your otel metric to Prometheus pipeline to be up AND your Prometheus server to be up.

Compare that to the vanilla HPA which is entirely cluster local, and “simple”.

Generally the simple approach is the most stable approach.

Re: Kubernetes horizontal pod autoscaling powered by an OpenTelemetry-native tool

#5
post #3

While useful, this is a more fragile autoscaling solution that HPA out of the box. It requires your otel metric to Prometheus pipeline to be up AND your Prometheus server to be up. Compare that to the vanilla HPA which is entirely cluster local, and “simple”. Generally the simple approach is the most stable approach.

HPA still requires metrics-server to be up which it’s using to obtain current pod resource usage

Re: Kubernetes horizontal pod autoscaling powered by an OpenTelemetry-native tool

#6
post #3

While useful, this is a more fragile autoscaling solution that HPA out of the box. It requires your otel metric to Prometheus pipeline to be up AND your Prometheus server to be up. Compare that to the vanilla HPA which is entirely cluster local, and “simple”. Generally the simple approach is the most stable approach.

True, but that approach is also limited in what it can autoscale on, namely Utilization metrics. They are not always good data to make scaling decisions on (covered in the article).

Re: Kubernetes horizontal pod autoscaling powered by an OpenTelemetry-native tool

#7
post #4

keda also works for this and supports many backends

Yes, it probably would be able to do the same logic as in the blogpost with the Prometheus scaler: https://keda.sh/docs/2.16/scalers/prometheus/

I might give it a go in a follow-up :-)