Kubernetes networking: service, kube-proxy, load balancing
You will explore ClusterIP, NodePort, and LoadBalancer service types and dive into their implementations using iptables rules.
You will also discuss advanced topics like preserving source IPs, handling terminating endpoints, and integrating with cloud load balancers.
Consider a two-tier application consisting of two tiers: the frontend tier, which is a web server that serves HTTP responses to browser requests, and the backend tier, which is a stateful API containing a list of job titles.
The command above provides deployment information, but it'd be great to get information about the individual pod, like the IP address or node it was assigned to.
You can retrieve the pod's IP address by appending -l app=backend to get only pods matching our deployment and -o wide so that the output includes the pod IP address.
Instead of reaching the Service by its IP address, you can assign a friendly name and rely on the DNS to translate it to an IP address.
