Oluwatosin Oladayo Aramide

One helm install, three jobs: the pod network, kube-proxy's whole duty in eBPF, and BGP from every node to its leaf pair's anycast gateway. Plus the consent chain that keeps VIP announcements deliberate, and the anycast peering quirk worth knowing.

kubeadm the deliberate way: a load-balanced control-plane endpoint before anything else, stacked etcd split across leaf pairs, no kube-proxy by design, and the NotReady checkpoint that makes Part 8 make sense.

One golden image, one netplan file per node: LACP bonds into the vPC pairs, out-of-band management, the virtio link-speed trap that silently breaks 802.3ad, and the switch side of every bond.

Wiring Active/Active firewalls into the fabric: four eBGP sessions, thirteen prefixes up and one default down, device-bound NAT, two DNAT pinholes for all inbound traffic, and the vPC SVI timer lesson.

VXLAN tunnels between loopbacks, EVPN as the directory, anycast gateways everywhere, and the route-target auto trap that silently empties eBGP fabrics. With the complete overlay configs for all twelve switches.

Twelve switches become a fabric: loopbacks, /31s, jumbo MTU, and eBGP as the only routing protocol. Plus the promised look inside a vPC leaf pair, and the three-command verification that proves the underlay.

How my bare-metal k8s cluster gets cloud-style LoadBalancer IPs: Cilium allocates a VIP, every node advertises it over eBGP to the NX-OS leaves, and the fabric ECMPs traffic into the cluster. Full walk from IPAM pool to leaf routing table.

One Linux box, a pile of QEMU VMs, and a bridge per cable. Sizing the host, the overcommit that makes it affordable, image conventions, and driving it all from the API.

A firmware setting decides whether each ConnectX port wakes up speaking Ethernet or native InfiniBand. My cards run both at once, and the same verbs binaries push bytes over either. One mstconfig line to change your NIC's religion.