How We Found 7 TiB of Memory Just Sitting Around

Re:How We Found 7 TiB of Memory Just Sitting Around by fells on Saturday November 01, 2025 @12:14AM (#45779195)

>you just gave every namespace a vector instance that was responsible for that namespace and pods within.

Vector is a daemonset, because it needs to tail the log files on each node. A single vector per namespace might not reside on the nodes that each pod is on.

[ Parent | on HN ]

Re:How We Found 7 TiB of Memory Just Sitting Around by stackskipton on Saturday November 01, 2025 @10:54AM (#45782091)

I think DaemonSet is to reduce network load so Vector is not pulling logs files over the network.

We run Vector as Daemonset as well but we don't have a ton of namespaces. Render sounds like they have a ton of namespaces running maybe one or two pods since their customers are much smaller. This is probably much more niche setup then many users of Kubernetes.

[ Parent | on HN ]

Re:How We Found 7 TiB of Memory Just Sitting Around by ahoka on Saturday November 01, 2025 @12:04PM (#45782741)

That's where the design is wrong.

[ Parent | on HN ]