Kubernetes networking is a pain 🛜
In Episode 1, I got all the services listed on my Kubernetes cluster , but everything was running inside the cluster as containers. To mimic how Uber’s Gateway API works, I needed to take the gateway outside the cluster.
🧱 That's when the first challenge hit: service discovery broke. Containers inside the cluster can talk to each other easily, but from the outside, it's a different story. To fix this, I configured RBAC to allow external requests to the cluster. This let me retrieve the services and the pod IPs running them - so far, so good.
🔐 Then came the next hurdle: these pod IPs are only meaningful inside the cluster. Any requests coming from outside? They can’t reach the pods at all. Right now, I’m exploring whether a service mesh might help route traffic properly, or if there’s another way to bridge this gap. Stay tuned for Episode 3, where I dive into the solution and finally get the external gateway fully functional.
Also find a brain rot version of architecture diagram of what I am trying to achieve.
Github : https://lnkd.in/gxR_JKds
Reference : https://lnkd.in/gg7CEaYn
Top comments (0)