Workload Resilience

Configure Kubernetes workloads to survive node failures, scale under load, and tolerate platform upgrades without service disruption.

Pod Ownership

Deploy workloads as part of a ReplicaSet (via Deployment) or StatefulSet. Do not use naked pods or DaemonSets for application workloads — they lack proper lifecycle management for updates, scaling, and recovery.

Required for: Telco (mandatory), Far-Edge (mandatory), Extended (mandatory), Non-Telco (optional)

Pod Scheduling

Pods should not use nodeSelector or nodeAffinity unless the workload requires specialized hardware (e.g., GPUs, SR-IOV NICs). Hardcoded node placement reduces cluster flexibility and causes deployment failures when specific nodes are unavailable.

Required for: Non-Telco (mandatory), all others (optional)