From the course: Certified Kubernetes Application Developer (CKAD) Cert Prep

Unlock this course with a free trial

Join today to access over 25,300 courses taught by industry experts.

Analyzing network access problems

Analyzing network access problems - Kubernetes Tutorial

From the course: Certified Kubernetes Application Developer (CKAD) Cert Prep

Start my 1-month free trial Buy for my team

Analyzing network access problems

“

- In this video, we'll talk about network problems. So different elements are required when a user accesses an application. Through DNS, the request reaches ingress. Ingress has rules that connect the incoming request to a service by referring to the service name. And the service connects to pods based on labels and selectors. And to troubleshoot application access, you should analyze it in this order. First, does the DNS request read ingress? Is there an ingress rule that connects the incoming request to a service? And does the service connect to the pods accessing the right labels? If you want to test if a process is running as expected inside the pod but not accessible from the outside, it may also be useful to connect to the pod using port forwarding. Use kubectl port-forward myweb on 8080:80, for instance, to access your pod on port 8080. Let's have a look at an example where I am going to use scroll to myapp.local. And oh boy, couldn't connect to server. Well, let's check it…

Contents