Register staged Cilium platform application and retire Talos‑managed Flannel
The latest main push introduces a new Cilium platform application through GitOps, replaces the legacy Talos‑managed Flannel configuration, and adds a dedicated cutover verification script. It also bumps the image chart revision and adjusts upstream test expectations, all aimed at moving Cilium to primary CNI on every node while preserving Multus and Flannel manifests.
Implementation: new Cilium patches and README updates
Two YAML files under .talos/patches/ were added – cilium-cni-rollback.yaml and cilium-cni.yaml – which define a rollback configuration that disables the Talos‑managed CNI (name: flannel). The README in clusters/homelab/platform/cilium/README.md was expanded to explain that the platform‑cilium registration now has automatic sync disabled, that operator replicas stay off the smallest worker (zimaboard-2), and describes the standalone node-migration.yaml selector used during the cutover stage after the chart installs its CRD. These changes ensure Cilium writes its primary CNI manifest on selected nodes while keeping existing Multus and Flannel files intact.
Verification and testing gaps
I have not executed the newly added scripts/cilium-cutover-check.py or the updated scripts/ci/uptime-kuma-check-test.py yet, so the catalog validation numbers shifted from (62,56) to (63,56) etc. The offline static checks also lost their stage‑test invocation. A concrete next step is to spin up a non‑production cluster, run the cutover check against the Kubernetes JSON snapshot, and confirm that primary pod IPs fall inside the Cilium pool without duplicate endpoints. Once verified, re‑run the Rego policy tests and the harbor image chart lint.
Platform team takeaway: retire Talos Flannel and enable controlled rollout
For any GitOps pipeline managing network components, the pattern here is clear: replace an external provider’s managed CNI (Talos Flannel) with a self‑hosted Cilium deployment, guard the transition with a node-migration selector, disable automatic sync for the platform application, and perform a separate cutover verification before promoting the chart. This reduces reliance on third‑party patches, limits exposure of legacy configurations, and makes rollback straightforward by applying the rollback yaml only after Cilium has taken over primary CNI on all nodes.