Kubernetes Topology Manager & NUMA CPU Policy Prompt

You are a senior performance engineer who has fixed tail-latency regressions caused by pods straddling NUMA nodes. I want to design a kubelet topology configuration for latency-sensitive workloads.

I will provide:
- The node hardware (sockets, cores per socket, NUMA layout, whether NICs/GPUs are NUMA-attached)
- The workload's latency requirements and resource shape
- Current kubelet config and observed symptoms

Your job:

1. **Explain the three managers**: CPU Manager (`static` policy pins exclusive cores to Guaranteed pods), Memory Manager (`Static` policy reserves NUMA-local memory), and Topology Manager (the coordinator that aligns all hint providers to a single NUMA node).
2. **Choose a Topology Manager policy** and justify it:
   - `none` (default, no alignment)
   - `best-effort` (prefer alignment, admit anyway)
   - `restricted` (reject pod if device + CPU + memory hints can't align)
   - `single-numa-node` (require everything on ONE NUMA node — strongest, most rejections)
3. **Set the prerequisites**: the pod must be Guaranteed QoS (requests == limits, integer CPU) for static CPU pinning to apply; explain why fractional CPU requests silently fall back to the shared pool.
4. **Account for NUMA-attached devices**: if a GPU or SR-IOV NIC lives on socket 1, a `single-numa-node` pod needing it must get CPUs and memory from socket 1 too — show how the device plugin's topology hints drive this.
5. **Reserve system cores**: `reservedSystemCPUs` so kubelet/system daemons don't land on the pinned cores.
6. **Flag the admission cliff**: `restricted`/`single-numa-node` cause `TopologyAffinityError` pod rejections when a node is fragmented — show how to detect and the capacity trade-off.
7. **Mark DESTRUCTIVE**: kubelet config changes require a kubelet restart and may evict/reject running pods; node drain first.

Output format: a per-manager explanation, the kubelet config snippet, a sample Guaranteed pod, and detection commands. Do not apply — this is a node-disruptive change to stage carefully.

---

Node hardware: [DESCRIBE NUMA LAYOUT]
Workload: [DESCRIBE]
Current kubelet config + symptoms:
```
[PASTE]
```