Home Configurator Sizing guide Docs GitHub

Helm values generator

Size your ImageEngine Kube cluster.

Turn a few workload knobs into a starting-point values-override.yaml. These are bench-from numbers — re-measure after deploying. See the sizing guide for the full rationale.

Getting started

Advanced

Cloud provider

Self-managed clusters have no cloud LB — front the edge with MetalLB or NodePort.

Requests / sec (to the cluster) 100/s

10/s10,000/s

Total edge ingress. Cache layers pare this down: ~90% hit at Varnish, ~75% of the rest at OSC — so 1000/s ≈ 100/s at the backend and ~25/s of image processing.

Total origin image size 1 TB

10 GB100 TB

Origin images to cache 30%

10%100%

Fraction of your origin catalog kept in OSC. Processed variants add ~2× more (20 variants/origin at ~10% of origin size each).

Cluster

Worker node RAM 8 GiB

4 GiB64 GiB

Assumes X GiB RAM = X/2 vCPU. Drives node-count estimates, processor pod size, and caps Varnish memory/disk to your nodes.

Environment

Logging

Edge access log

Per-request structured JSON. High volume — Auto disables it in production or above ~100/s to save I/O, CPU & storage.

Origin-fetcher log

One record per origin fetch (cache misses on the cold path) — far lower volume than access logs, so it stays on by default.

OpenTelemetry tracing

Computed footprint

values-override.yaml

Install with override

Maintained by ScientiaMobile kube.imageengine.io