Switch language한국어
Back to the list

Veltrix and the Day the Trace Loops Broke

TL;DR AI

Key summary

2 min read
  1. Veltrix 2.4.1’s original autoscaling layer overprovisioned workers and triggered observability problems plus major latency spikes.

  2. After repeated fixes failed, the team removed that layer and deployed veltrim, a Kubernetes admission controller with Lua rules.

  3. Veltrim blocks risky scale-downs using CPU and cache-miss checks, helping protect warm pods and LLM caches.

  4. The new setup reduced worker churn, stabilized pod behavior, and lowered p95 latency, though it added some kube-apiserver CPU overhead.

Read the original