#Tag

Posts tagged "networking"

← All posts

  1. The best migrations delete more than they install

    Nobody chose our network stack - it accreted one default at a time, and every component was one more thing to version, patch, debug and alert on. Landing on Cilium wasn't an adoption; it was a demolition schedule, and the stack left standing is smaller than the one we started with.

  2. Observe first, deny second

    Everyone writes network policy from the architecture diagram, and the diagram is always wrong. The only allowlist that survives contact with production is one written from the flows you actually watched - applied out-of-band, proven enforcing, and only then handed to GitOps.

  3. SNAT ate my source IP

    A LoadBalancer service with the default traffic policy rewrites every incoming packet's source to the node's own address, so by the time a network policy sees it, the real client is gone. You cannot allowlist a sender the network has already erased.

  4. The most secure inbound port is the one you never open

    Exposing self-hosted services to the internet with zero open ports, zero port-forwarding, and the origin's IP never leaving the building.