On a fresh node that can take five minutes. During a traffic spike, five minutes is the whole incident.

Most of that time is avoidable, because most of it is spent fetching things that have not changed since the last Pod started.

Default start = pull the image + download the model + load it, every single time
Cached start  = image and model are already on disk, so only the load remains

My autoscaling guide explained why slow cold starts make scaling hard. This post is about making them short.

Where the time goes

A cold start has four phases. Each is limited by something different.

Every phase is “size divided by speed”. Take an 8B model in 16-bit (16 GB) and an 8 GB serving image as an example:

These speeds are round numbers for illustration. Yours will differ, but the shape rarely does: the two downloads are most of the wait.

Four ways to start, compared

Now remove the phases one at a time, using the same example numbers:

Two things stand out:

• Caching the model is the biggest single win. It removes the largest phase outright.
• After that, disk speed is everything. Setup C loads from network storage at 200 MB/s. Setup D loads from NVMe at 2,000 MB/s. Same files, ten times faster.

From A to D is a 10x improvement, with no change to the model or the GPU.

Step 1: put the model on a volume

By default vLLM downloads from the Hugging Face Hub into a cache directory inside the container. When the Pod dies, the cache dies with it.

Point that cache at a persistent volume, and the download happens once.

# model-cache-pvc.yaml
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: model-cache
  namespace: llm
spec:
  accessModes:
    - ReadWriteMany
  resources:
    requests:
      storage: 100Gi

kubectl apply -f model-cache-pvc.yaml

ReadWriteMany lets several replicas mount the same volume, so they all share one copy. It needs a storage class that supports it (NFS, a managed file store, or a distributed file system). With ReadWriteOnce, each replica needs its own claim and its own download.

Fill the cache with a Job

Download the model once, ahead of time, instead of making the first serving Pod do it:

# model-download-job.yaml
apiVersion: batch/v1
kind: Job
metadata:
  name: model-download
  namespace: llm
spec:
  backoffLimit: 3
  template:
    spec:
      restartPolicy: OnFailure
      containers:
        - name: download
          image: python:3.12-slim
          command:
            - bash
            - -c
            - pip install -q huggingface_hub && hf download "$MODEL"
          env:
            - name: MODEL
              value: "<org>/<model>"
            - name: HF_HOME
              value: /cache
            - name: HF_TOKEN
              valueFrom:
                secretKeyRef:
                  name: hf-token
                  key: token
                  optional: true
          volumeMounts:
            - name: cache
              mountPath: /cache
      volumes:
        - name: cache
          persistentVolumeClaim:
            claimName: model-cache

kubectl apply -f model-download-job.yaml
kubectl -n llm wait --for=condition=complete job/model-download --timeout=30m

HF_HOME tells the Hugging Face tools where the cache lives. The token is only needed for gated models. On older versions of huggingface_hub, the command is huggingface-cli download instead of hf download.

Mount it in the serving Pod

Add three things to the vLLM container: the same HF_HOME, the volume, and a switch that forbids downloads.

# excerpt from the vLLM Deployment
      containers:
        - name: vllm
          image: vllm/vllm-openai:latest
          args: ["--model", "<org>/<model>"]
          env:
            - name: HF_HOME
              value: /cache
            - name: HF_HUB_OFFLINE
              value: "1"
          volumeMounts:
            - name: cache
              mountPath: /cache
              readOnly: true
      volumes:
        - name: cache
          persistentVolumeClaim:
            claimName: model-cache

HF_HUB_OFFLINE=1 is the important line. Without it, a Pod that cannot find the model quietly starts a 16 GB download. With it, the Pod fails immediately and tells you the cache is missing.

A fast, loud failure beats a slow, silent one.

Pin the image to a specific version tag in real deployments. latest is here only to keep the example short.

Step 2: pre-pull the image

The serving image is large because it carries CUDA libraries and PyTorch. A node that has never run it must pull all of it before the container can start.

A small DaemonSet fixes that by pulling the image on every GPU node as soon as the node joins:

# vllm-image-prepull.yaml
apiVersion: apps/v1
kind: DaemonSet
metadata:
  name: vllm-image-prepull
  namespace: llm
spec:
  selector:
    matchLabels:
      app: vllm-image-prepull
  template:
    metadata:
      labels:
        app: vllm-image-prepull
    spec:
      nodeSelector:
        nvidia.com/gpu.present: "true"
      tolerations:
        - key: nvidia.com/gpu
          operator: Exists
          effect: NoSchedule
      initContainers:
        - name: pull
          image: vllm/vllm-openai:latest
          command: ["sh", "-c", "exit 0"]
      containers:
        - name: pause
          image: registry.k8s.io/pause:3.10

kubectl apply -f vllm-image-prepull.yaml

The init container runs the vLLM image just long enough to exit, which forces the node to download it. The tiny pause container then keeps the Pod alive without using resources.

Use the same image tag here as in your Deployment. Otherwise you pre-pull an image nobody runs. The nvidia.com/gpu.present label is set by the GPU Operator’s feature discovery; change the selector if your GPU nodes are labelled differently.

Step 3: pick the right storage

Once nothing is downloaded, the load phase is all that is left, and it runs at the speed of your disk.

There is no single winner. It is a trade between speed and convenience:

The “both” option is common on autoscaled clusters. An init container copies the model from the shared volume to the node’s NVMe the first time a node is used. Later Pods on that node start at full NVMe speed.

One free speedup is worth knowing. Linux keeps recently read files in memory. If a Pod restarts on the same node soon after, the weights may still be in the page cache, and the load takes seconds regardless of the disk.

What about baking the model into the image?

It is tempting: one artifact, nothing to mount.

For a small model in an air-gapped cluster, baking it in can be the simplest thing that works. For anything large or frequently updated, the volume wins.

Do not let Kubernetes kill a slow starter

Even a fast start takes longer than a typical web app. Tell Kubernetes to wait, or it will restart the Pod mid-load and make things worse:

          startupProbe:
            httpGet:
              path: /health
              port: 8000
            periodSeconds: 5
            failureThreshold: 120
          readinessProbe:
            httpGet:
              path: /health
              port: 8000
            periodSeconds: 5

That allows up to 10 minutes (120 checks, 5 seconds apart) before the Pod is considered failed. Once startup passes, the readiness probe takes over. A short periodSeconds matters here: it is how quickly a ready Pod starts receiving traffic.

Measure your own cold start

Do not trust the tables above. Time the real thing:

kubectl -n llm delete pod -l app=vllm --wait=false

kubectl -n llm get pods -l app=vllm -w

Watch how long the new Pod spends in each state:

For the exact split inside the container, read the startup log. vLLM prints how long loading the weights took:

kubectl -n llm logs -l app=vllm | grep -i -E "load|took|seconds"

Whichever phase is longest is the one to fix next.

Cheat sheet

Cold start        = time from Pod created to first request served
Image pull        = downloading the serving image; removed by pre-pulling
Model download    = fetching weights from the Hub; removed by a cached volume
Weight load       = reading weights from disk into the GPU; limited by disk speed
HF_HOME           = where Hugging Face tools keep their cache; point it at a volume
HF_HUB_OFFLINE=1  = forbid downloads, so a missing cache fails fast instead of slowly
Download Job      = fills the cache once, before any serving Pod needs it
ReadWriteMany     = a volume several replicas can mount at once and share
Pre-pull DaemonSet = pulls the image on every GPU node ahead of time
Node-local NVMe   = the fastest place to load from, but lost with the node
Page cache        = files recently read are still in memory, so restarts are quick
startupProbe      = tells Kubernetes a Pod is allowed to take minutes to start
Rule of thumb     = never download at start time, then load from the fastest disk you have

Fast starts make autoscaling practical: a replica that is ready in 30 seconds can react to a spike that a 5-minute replica would miss. For how big the weights are in the first place, see How Much GPU Memory Does an LLM Need? and LLM Quantization, Simply.