[Verse 1] When your traffic needs a gateway to the cluster door Ingress resources are what you're looking for They route the requests from outside to in Let's learn to list them, that's where we begin [Chorus] kubectl get ingress dash A Shows them all across the way Every namespace, every route Traffic flowing through and through Get ingress dash A today Lists them all without delay [Verse 2] The dash A flag means all namespaces wide No single namespace to hide behind You'll see the hosts and the backend names The rules that guide the traffic games [Chorus] kubectl get ingress dash A Shows them all across the way Every namespace, every route Traffic flowing through and through Get ingress dash A today Lists them all without delay [Bridge] Name and namespace in the first columns you'll find Class and hosts showing how they're designed Address and ports tell you where they bind Age shows how long they've been assigned [Verse 3] From default namespace to kube-system too Production, staging, development crew One single command shows the complete view All ingress resources displayed for you [Chorus] kubectl get ingress dash A Shows them all across the way Every namespace, every route Traffic flowing through and through Get ingress dash A today Lists them all without delay [Outro] So when you need to see the traffic flow All ingress resources in one show Remember the A flag, let your knowledge grow kubectl get ingress dash A, now you know
← 5 Troubleshooting Common Issues | Create from literal values →