Topic 4: Device And Network Plugins

Official baseline: (The Kubernetes Authors, 2026a, 2026b). My working version: Plugins let Kubernetes understand capabilities it does not own directly: GPUs, hardware, and custom networking.

Mental Model

Plugins let Kubernetes understand capabilities it does not own directly: GPUs, hardware, and custom networking.

Notes

  • Device plugins advertise allocatable hardware to kubelet.
  • Network plugins implement the cluster network contract.
  • Plugin failure often looks like scheduling or Pod startup failure.

Homelab Angle

This is where Kubernetes meets real hardware. Keep notes per node.

Verify It

  • Read the object status before changing the manifest.
  • Check events for the controller or node that is actually complaining.
  • Confirm the official source linked below still matches the cluster version you run.

Common Failure Modes

  • Treating the YAML object as the system, instead of one input to a reconciliation loop.
  • Debugging from outside the cluster when the failure only exists inside cluster networking or node state.
  • Forgetting that Kubernetes version, addon version, and runtime behavior are linked.

Sources

  • Device Plugins - source path: content/en/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins.md, commit 8cc9e19b8eec8d5cf49eacd66f86a81648edb1a0.
  • Network Plugins - source path: content/en/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins.md, commit 8cc9e19b8eec8d5cf49eacd66f86a81648edb1a0.
  • Kubernetes documentation is licensed under CC BY 4.0; these notes are original commentary and link back to the official source.
The Kubernetes Authors. (2026a). Device Plugins. https://kubernetes.io/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/
The Kubernetes Authors. (2026b). Network Plugins. https://kubernetes.io/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/