Kubernetes Networking Exercises
Diagnose from the same source Pod
For each case, pick the next test before revealing the explanation. Assume the application expects the same HTTP host and path for each probe.
The name returns NXDOMAIN, and the ClusterIP returns HTTP 200.
Inspect the source Pod's DNS search domains and verify the Service name, namespace, and cluster domain. This request reaches the Service successfully by address.
The name resolves, the ClusterIP times out, and the backend Pod IP returns HTTP 200.
Compare Service port and targetPort with the EndpointSlice ports and endpoint conditions. Check Service forwarding and policy evaluation. A single successful backend test proves only that one path works.
Internal HTTP requests work, but the public gateway returns 502.
Check the route parent conditions, the configured upstream protocol and port, and load balancer health. Identify the upstream selected by the gateway and use its logs to narrow down the failure.
Check your networking understanding
Continue with the Layer 3 through Layer 7 troubleshooting walkthrough.
Calculate GKE Pod IP capacity
Start with a /16 and 110 Pods per node. Compare the result with 64 Pods per node. The model assumes one homogeneous IPv4 Pod secondary range and uses the documented block allocation formula. Primary subnet capacity, system Pods, quotas, mixed pools, and upgrade headroom affect usable capacity.
- Pod range addresses
- 65,536
- Pod block per node
- /24
- Addresses reserved per node
- 256
- Theoretical node blocks
- 256
- Theoretical Pod slots
- 28,160
Check your GKE networking understanding
Continue with the GKE load balancer diagnosis.
Model Istio traffic and retries
Change the target canary weight and compare the two route shares. Observed traffic can vary from the weights. For retries, change the hop count and attempts to see an upper bound that assumes every hop retries fully. Deadlines, cancellation, and actual failures affect the observed result.
Track the service mesh lab
0 of 9 complete
Check your Istio understanding
Continue with the Payment-to-Order walkthrough.