| Mode | Description | Advantages | Disadvantages |
|---|---|---|---|
| Userspace | Initial default mode, watches Kubernetes API server for changes in services and endpoints, creates userspace proxy server for each service port | - Easy to set up | - Poor performance - High resource consumption - Potential port conflicts |
| Iptables | Modern default mode, watches Kubernetes API server for changes in services and endpoints, creates iptables rules for each service port | - Better performance and scalability than userspace mode | - High latency for large clusters - Lack of health checks - Difficulty in debugging |
| IPVS | Alternative mode, uses IP Virtual Server (IPVS) for layer-4 load balancing, watches Kubernetes API server for changes in services and endpoints, creates IPVS rules for each service port | - Higher performance - Lower latency - More load balancing algorithms - Health checks - Graceful termination |
- Requires additional configuration - Less commonly used |
Created
August 30, 2023 09:37
-
-
Save EliFuzz/e6c769b0797860fe8f4ea4c6c3b2185b to your computer and use it in GitHub Desktop.
Comparison Table: Kube-proxy Modes
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment