fix: upgrade Cilium to 1.19.7 to resolve operator CrashLoopBackOff #1
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/cilium-operator-crash"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Cilium operator has been CrashLoopBackOff for ~3 days on the siriussec node.
Root cause: Cilium 1.18.13 operator tries to set up a field indexer for
TLSRouteatgateway.networking.k8s.io/v1alpha2, but the cluster's TLSRoute CRD only supportsv1andv1alpha3. The operator panics fatally on startup.Fix: Upgrade Cilium chart from
1.18.13→1.19.7. The 1.19 series fixed the gateway API handling to work with thev1/v1alpha3TLSRoute layout.Current state:
publicclass): Accepted/Programmed=TrueVerification after merge:
kubectl get pods -n kube-system -l app.kubernetes.io/name=cilium-operator→ 1/1 Runningkubectl get nodes→ all Ready, no new taintscurl -sI http://10.10.0.1via the Gateway should still workTest plan
flux reconcile kustomization flux-system)