Skip to content
Multi-Site Kubernetes BGP Anycast Architecture

Multi-Site Kubernetes Cluster with BGP Anycast

The engineering question How do services stay reachable when a site or path fails? I built and operate the routing and cluster integration in my own lab, using BGP, VPNs and Cilium. The result is a working environment for observing routing and service-discovery behaviour, with the architecture described below. It does not establish an availability guarantee; the next useful work is repeatable recovery measurement. The June 2026 inventory counted 13 Kubernetes nodes across two sites: 7 in the Netherlands and 6 in Greece. Earlier references to 7 described the Netherlands cluster alone. A Netherlands snapshot from 28 October 2026 still records 7; a comparable current whole-estate count has not been verified. Historical counts are not live capacity. ...

December 16, 2025 · Updated October 29, 2026 · 3 min · Kyriakos Papadopoulos
Portfolio site architecture: GitLab CI pipeline to dual-cluster DMZ deployment

Portfolio Site: Hugo + Live Chaos Engineering

This is the site you’re looking at. It started as a Hugo portfolio deployed to DMZ nginx containers via GitLab CI and AWX. Then I added a status page that shows the VPN mesh in real-time. Then I added the ability to kill tunnels from the browser. Then I added a log terminal that streams syslog from the firewalls while you watch. It kept going. Try it on the status page – click tunnel edges on the graph, hit Kill, and watch what happens. ...

December 16, 2025 · Updated June 19, 2026 · 5 min · Kyriakos Papadopoulos