Skip to navigation
NVKE telemetry pipeline (NKTP)Guides

Size resources

View as Markdown

Default budgets are per Pod. Configure collector resources under <component>.kubernetes.resources and allocator resources under <component>.kubernetes.targetAllocator.resources.

ComponentCPU / memory requestCPU / memory limit
Node collector1 / 2 GiB2 / 4 GiB
Large-target collector2 / 8 GiB4 / 16 GiB
Metrics, logs and traces gateways200m / 512 MiB4 / 8 GiB
Cluster event reader1 / 512 MiB4 / 1 GiB
Watchdog500m / 512 MiB4 / 1 GiB
Node Target Allocator250m / 2 GiB2 / 4 GiB
Large-target and watchdog Target Allocators250m / 1 GiB1 / 2 GiB
Self-telemetry sidecar, watchdog and gateways20m / 64 MiB200m / 256 MiB
Self-telemetry sidecar, other Collectors10m / 32 MiB100m / 128 MiB

Node collectors use a 3276MiB GOMEMLIMIT. Gateways use 7 GiB, large-target collectors use 8 GiB and watchdog uses 768 MiB. Tune runtime memory targets and queues together with container limits. The node metrics queue holds 32 MiB to admit larger scrapes before batching.

HPA targets are relative to requests. Increasing limits does not raise the scaling threshold. Reserve node capacity for growth and failure recovery, and start enough scraper replicas to absorb large initial loads. These budgets do not guarantee a particular series count. Validate allocator discovery and reassignment under load, especially after restarts.

See Large-target metrics for sizing the pool for large scrape responses, and Backpressure for how queues and the memory limiter behave when a component is saturated. See Self-telemetry sidecars for how the sidecar sizes were chosen.