"I applied an Ingress — and it doesn't respond. Why?"
A local Kubernetes classic: you write an Ingress manifest, kubectl apply, open the browser — and silence. The thing is, an Ingress by itself is just rules. Until there's an Ingress controller in the cluster (Traefik, NGINX) that reads those rules and accepts traffic, nothing works. Straight from the docs: "Only creating an Ingress resource has no effect."
And the second most popular k3d pain: the loadbalancer port mapping is set ONLY at cluster creation. Forgot -p "8081:80@loadbalancer"? You'll have to recreate the cluster.
In the new article (part 11) I break networking down layer by layer:
• how Pods find each other by name via CoreDNS (and why the short name only works inside its own namespace);
• three ways to reach in from outside: port-forward, NodePort, Ingress — and when to use which;
• Traefik out of the box in k3d and the whole chain: curl → port 8081 → Traefik → Service → Pod;
• why http://myapp.localhost opens in Chrome but curl says "could not resolve host" (spoiler: RFC 6761, and it's not a bug).
Read it and stop fighting your cluster's networking: https://dorokhovich.com/blog/local-k8s-networking-and-ingress?utm_source=devto&utm_medium=syndication&utm_campaign=local-k8s-networking-and-ingress
Top comments (0)