Diegolden

Topic 3: Addons As Platform Dependencies

2 min read

Topic 3: Addons As Platform Dependencies

Official baseline: (The Kubernetes Authors, 2026b, 2026a). My working version: Addons are not optional once workloads depend on them. They become part of the platform SLO.

Mental Model

Addons are not optional once workloads depend on them. They become part of the platform SLO.

Notes

  • CoreDNS, CNI, ingress, metrics, and storage plugins deserve lifecycle tracking.
  • Addons need resource requests too.
  • Version skew between addons and cluster can create subtle failures.

Homelab Angle

Inventory addons the same way you inventory applications.

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

  • Kubernetes Components - source path: content/en/docs/concepts/overview/components.md, commit 8cc9e19b8eec8d5cf49eacd66f86a81648edb1a0.
  • Cluster Administration - source path: content/en/docs/concepts/cluster-administration/_index.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). Cluster Administration. https://kubernetes.io/docs/concepts/cluster-administration/
The Kubernetes Authors. (2026b). Kubernetes Components. https://kubernetes.io/docs/concepts/overview/components/

Graph View

Backlinks