The Voiceware Service Template: Small YAML, Big Responsibility
How a short Service template binds a logical name to selected pods and a target port.
networking
Why I Later Exposed Voiceware on NodePort 30080
The practical reason for adding a simple external access path while validating the web deployment.
Why the First Voiceware Web Service Used ClusterIP
Why internal reachability was the safer default during the first deployment slice.
Internal Services vs External Services in Voiceware
How I separate east-west service communication from user-facing exposure.
NodePort Was a Validation Step, Not the Whole Networking Story
How I think about the later web-app NodePort in the context of a production edge design.
Ubuntu 18.04 on a Lab Machine: The Networking Commands I Kept Reusing
Ubuntu 18.04 was a good excuse to stop relying on desktop network icons and start reading interface state, routes, sockets and DNS configuration directly from the system.
Port 80 Appears Twice, but the Responsibilities Are Different
Distinguishing an Nginx listener from the web application service contract even when both use port 80.
Tailscale with Docker: Host-Level Tailnet or Per-Container Sidecar?
I choose the networking boundary before I add Tailscale to a Docker stack, because the two patterns create different operational models.
How I Read Tailscale Status: Direct Paths, Relays and What They Actually Tell Me
A peer marked online is only the start. I also care whether the path is direct, relayed and stable enough for the workload.
Docker Networks Hid Less Once I Drew the Packet Path
Container networking stopped feeling magical when I separated host routing, bridge interfaces, NAT and the application socket.
When a Docker Service Name Does Not Resolve from Caddy
Docker DNS only resolves service names inside the networks where those services actually meet.
Container Ports Are Documentation and a Runtime Contract
How service ports made Voiceware component boundaries visible.
eBPF/XDP: The Verifier Passing Does Not Mean Your Network Program Is Safe
The verifier proves classes of memory and control-flow safety. It does not prove that returning the wrong XDP action, updating the wrong map, or attaching at the wrong hook will preserve network connectivity.
DNS Lookup Time Belongs in an Edge Dashboard
A slow public request is not always slow application code; DNS resolution can consume a meaningful part of the user-visible path.
Socket Counts Are Capacity Clues, Not Health by Themselves
A rising established-connection count can represent normal load, a leak, slow clients or a downstream dependency holding sockets open.
Packet Drops Are More Actionable Than Raw Bandwidth
High interface traffic can be completely healthy, while a small but sustained drop rate can damage voice, APIs and tunnel reliability.