Posted April 29Apr 29 Let’s Start With What You Might KnowBy now, you’ve launched a container, wrapped it in a Pod, deployed it using a Deployment, and scaled it up to multiple Pods.But here’s the next problem:“Okay, my app is running inside Kubernetes… but how do I access it?”You try running:kubectl get pods -o wide And you see something like:NAME READY STATUS IP NODE myapp-xyz 1/1 Running 10.244.1.5 worker-node-1Great — but:That Pod IP is internalIt changes if the Pod dies and restartsAnd if you have 3 replicas… which IP do you even hit?That’s where Services come in...View the full article
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.