Networking
Цей контент ще не доступний вашою мовою.
The network stack that powers container and Kubernetes networking.
Overview
Section titled “Overview”Linux networking is the foundation for everything in Kubernetes—pod-to-pod communication, services, ingress, network policies. Understanding it helps you debug networking issues and understand how Kubernetes abstractions actually work.
Modules
Section titled “Modules”| # | Module | Description | Time |
|---|---|---|---|
| 3.1 | TCP/IP Essentials | OSI model, TCP vs UDP, subnetting, routing | 30-35 min |
| 3.2 | DNS in Linux | resolv.conf, dig, DNS debugging | 25-30 min |
| 3.3 | Network Namespaces | veth pairs, bridges, pod networking | 30-35 min |
| 3.4 | iptables & netfilter | Packet filtering, NAT, kube-proxy internals | 35-40 min |
Why This Section Matters
Section titled “Why This Section Matters”Almost every Kubernetes issue eventually involves networking:
- Pod can’t reach service? Understand routing and iptables
- DNS resolution failing? Know how Linux resolves names
- Network policy not working? Understand how netfilter works
- Performance issues? Could be network namespace or iptables overhead
Prerequisites
Section titled “Prerequisites”- System Essentials — Processes, filesystem
- Container Primitives — Namespaces concept
Key Takeaways
Section titled “Key Takeaways”After completing this section, you’ll understand:
- How TCP/IP works and how to troubleshoot connectivity
- How Linux resolves DNS and why containers have DNS issues
- How network namespaces create isolated network stacks (pod networking)
- How iptables/netfilter powers Kubernetes services and policies
Related Sections
Section titled “Related Sections”- Previous: Container Primitives
- Next: Security/Hardening
- Applies to: Every network-related Kubernetes concept