[Verse 1] When your service is running but pods seem to hide You need to discover what's working inside Behind every service there's endpoints to find The pods that are ready to serve and reply [Chorus] Get endpoints, get endpoints kubectl get endpoints service name Get endpoints, get endpoints Shows the pods that are backing your game IP addresses and ports in a line Ready pods that are working just fine Get endpoints, get endpoints That's the command you need to retain [Verse 2] Your service selector finds pods by their label But which ones are healthy and ready and able The endpoint controller keeps track of the state Only ready pods make it through the gate [Chorus] Get endpoints, get endpoints kubectl get endpoints service name Get endpoints, get endpoints Shows the pods that are backing your game IP addresses and ports in a line Ready pods that are working just fine Get endpoints, get endpoints That's the command you need to retain [Bridge] When traffic flows in through your service door Endpoints decide where it goes and what for No endpoints listed means no pods are ready Check your deployment keep traffic steady [Verse 3] Debug your service when things go wrong Use get endpoints to sing this song Empty results mean your pods aren't there Or readiness probes show they're not prepared [Chorus] Get endpoints, get endpoints kubectl get endpoints service name Get endpoints, get endpoints Shows the pods that are backing your game IP addresses and ports in a line Ready pods that are working just fine Get endpoints, get endpoints That's the command you need to retain [Outro] Service name after endpoints command Now you know where your ready pods stand
← List services | Test DNS resolution from inside the cluster →