Local Node Reconciliation and Separate Leader Setup

Local Node Reconciliation and Separate Leader Setup A sequence diagram generated by Archify. CiliumNode created / updated Reconcile local FDB / neighbor / route Every replica handles the node IP and allocated Pod CIDRs. CiliumNode deleted Remove obsolete local node entries Leader: CreateRoute / ReplaceRoute Configured aggregate10.100.0.0/20 points to leader ENI; not a per-node AWS route. Then update CiliumVTEPConfig endpoints Runtime does not call AWS DeleteRoute; uninstall cleanup is separately owned. CiliumNode events: local tunnel state only Separate leader setup: aggregate AWS routes, then VTEP Hybrid Node · on-premises · Sequence participant Hybrid Node on-premises Kubernetes API · CiliumNode / VTEP config · Sequence participant Kubernetes API CiliumNode / VTEP config Gateway Replicas · Local state on every replica · Sequence participant Gateway Replicas Local state on every replica VPC Route Table · routeTableIDs · Sequence participant VPC Route Table routeTableIDs Legend request default message