Advanced examples

Pod Labels and Affinities

How pods target burst nodes: nodeAffinity (provider, nodepool), podAffinity (co-locate to avoid egress), podAntiAffinity (spread for HA). Cloudburst treats any Pending pod with reason Unschedulable as demand; each NodePool sees all unschedulable pods and may create capacity.

nodeAffinity, podAffinity, podAntiAffinity: how pods target and co-locate on burst nodes — Pod labels and affinities: target nodes by provider, co-locate to avoid egress, or spread for HA.

Affinity examples

Node Node affinity No affinity, provider affinity (GCP only), nodepool affinity. Target specific clouds or NodePools. View example → Pod Pod affinity (co-locate) Co-locate related pods on the same node to avoid egress fees. Soft and hard affinity. View example → Pod Pod anti-affinity (spread) Spread replicas across nodes for high availability. Soft and hard anti-affinity. View example →