Skip to main content
Reflection developed this Kubernetes serving solution in partnership with Dell for on-premises deployments. Deploy Beam with the reflection-serving Helm chart. The chart deploys a Dynamo frontend that routes requests to SGLang or vLLM workers, using KV-aware routing. The frontend and every worker read the model from one PVC that you provide.

Prepare the cluster

Get the chart and configuration

Download the Helm chart and configuration files:
Download the chart
The archive unpacks into a serving directory:
serving
sglang-bf16.yaml
sglang-dflash.yaml
sglang-fp8.yaml
sglang-hicache.yaml
sglang-nvfp4.yaml
sglang-pdd.yaml
site-values.example.yaml
vllm-bf16.yaml
vllm-dflash.yaml
vllm-fp8.yaml
vllm-nvfp4.yaml
vllm-pdd.yaml
reflection-serving is the Helm chart. The YAML files beside it are values files: one engine file per deployment, optional feature files, and your site values. Set ENGINE_VALUES to your configuration: Edit site-values.yaml for your model storage and GPU nodes:
site-values.yaml

Scale out

Add this to site-values.yaml to scale to four replicas:
site-values.yaml

Prefill-decode disaggregation

PDD separates prompt processing from token generation. It can help with long prompts or different capacity needs for each stage. Aggregated serving avoids KV transfers and may suit shorter prompts or lower concurrency; the choice is workload dependent. The PDD files add two prefill replicas and one decode replica. Prefill workers transfer the KV cache to decode workers with NIXL over RDMA.
sglang-pdd.yaml

Install and verify

Install the chart
Once the frontend and workers are Ready, run the smoke test:
Run the smoke test

Production endpoint

Place your TLS and authentication gateway in front of beam-frontend:8000. The chart deploys one frontend; arrange frontend redundancy separately for high availability.

Remove the deployment

Remove the deployment
Last modified on October 16, 2026