[Verse 1] When you need to see what's running in your cluster space There's a command that shows you every service face Type kubectl describe and add svc right after Then the service name you're chasing after [Chorus] Describe the service, see what it connects Endpoints showing where the traffic directs Selector matching pods that qualify Port mappings tell you how the data flies K-U-B-E-C-T-L describe Shows you the service blueprint inside [Verse 2] Endpoints are the addresses where requests will go Each pod IP that matches what you need to know When selectors find the pods with matching tags The service routes the traffic without any lags [Chorus] Describe the service, see what it connects Endpoints showing where the traffic directs Selector matching pods that qualify Port mappings tell you how the data flies K-U-B-E-C-T-L describe Shows you the service blueprint inside [Bridge] Target port is where your app receives Service port is what the client believes Session affinity keeps connections true Load balancing spreads the work for you [Verse 3] Name and namespace tell you where it lives Type and cluster IP show what it gives Creation timestamp marks when it was born Labels and annotations keep it well-adorned [Chorus] Describe the service, see what it connects Endpoints showing where the traffic directs Selector matching pods that qualify Port mappings tell you how the data flies K-U-B-E-C-T-L describe Shows you the service blueprint inside [Outro] When your audiobook pods need to be found Describe the service keeps your traffic sound Endpoints, selectors working in harmony That's how Kubernetes serves your poetry
← Create a headless service (for StatefulSets) | DaemonSets (one pod per node — logging agents, monitoring) →