3 ms·
Using custom/external metrics is exactly what I was looking for, thanks! I think my misunderstanding comes from the distinction between "first party" sensors (
by deivid 2y ago
Using custom/external metrics is exactly what I was looking for, thanks!
I think my misunderstanding comes from the distinction between "first party" sensors (CPU scaler) and "third party" sensors (via "external metrics").
Is there a reason for this distinction? Will the CPU scaler eventually be pushed out of k8s as well?
- richardwhiuk 2y agoKubelet is already managing the CPU resource I guess from scheduling? I don't think there's any real movement on moving CPU scaler out of HPA.
- smarterclayton 2y agoCPU tracking is provided by the metrics API, which either reads kubelet metrics directly (the original, old, but simplest way), or a metrics adapter that reads the metrics from a third party collector and implements the API. The behavior is supported by the v1 api rules so no, it’s extremely unlikely to be moved out. That said, with GPU workloads gaining steam I wouldn’t be surprised if we added new “supported everywhere” metrics at some point.