Node Taints and Affinities

Scheduling and placement controls for Foundation workloads.

Agentic Friendly

Component Category

Cluster operations / scheduling and placement

Component Description

Node taints, tolerations, and affinities are Kubernetes scheduling controls used to steer workloads onto the right nodes.

Why It Is Used

In BullSequana AI Foundation, these controls help reserve specialized hardware for the workloads that need it most. They are especially important for GPU inference, high-storage services, and other components that should not compete with general-purpose workloads for the wrong node types.

Learn More

Platform placement

The platform uses these node labels and taints:

WorkloadNode labelTaint toleratedStrength
PostgreSQL (CloudNativePG)workload=high-memorydedicated=high-memoryPreferred; required with [common] enforce_affinity
Ceph OSDsworkload=storagededicated=storagePreferred; required with [common] enforce_affinity
vLLM and Triton GPU runtime profilesnvidia.com/gpu.present=truenvidia.com/gpuRequired
Time-sliced and fractional GPU profilesnvidia.com/device-plugin.config=timeslicing or fractioningnvidia.com/gpuRequired
Speaches in CUDA modeworkload=gpunvidia.com/gpuPreferred
Agent sandbox pods and the Kata runtimeworkload=sandboxworkload=sandbox (NoSchedule)Required

[common] enforce_affinity (COMMON_ENFORCE_AFFINITY, false by default) turns the database and storage preferences into required node affinity and their tolerations from PreferNoSchedule into NoSchedule. It does not change GPU placement. See GPU node configuration and Enable GPU for AI components.

Placement is not the only GPU control. In tenant namespaces, every GPU pod must be scheduled by KAI Scheduler into one of the tenant's GPU queues, which bound how many GPUs the tenant uses. See Tenant GPU scheduling.

Interacts With

  • KServe, vLLM, and KAI Scheduler, which manage GPU-aware model workloads.
  • Kata Containers, whose runtime runs only on the sandbox node pool.
  • Rook Ceph and PostgreSQL, when storage-heavy workloads should be steered to specific nodes.
  • Prometheus and Grafana, which help operators verify workload placement and resource behavior after scheduling rules are applied.

On this page