kube-proxy

Kube-proxy is a network proxy that runs on every node of a Kubernetes cluster.

  • Infrastructure
  • Network Services
Kube-proxy is a network proxy that runs on every node of a Kubernetes cluster. It implements the Kubernetes Service and Endpoints interfaces by dynamically managing the network rules that route traffic from each Service's virtual IP address to the correct backend pods. Operators rely on it to keep in-cluster and external requests connected to the right workloads automatically, with no manual routing.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

74/100 Good

Maintained
100last commit 17 days ago
Popular
47214 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
100256 MB minimum RAM, runs on ARM
Security check
75no serious findings, tests, OpenSSF Scorecard 5.3/10

Availability: platform listings confirmed yesterday

GitHub stars
214
Open issues
0
Last commit
2026-11-03
License
Apache-2.0
Activity
declining

Checked 2 days ago - source: GitHub (kubernetes/kube-proxy)

Resources & Compatibility

Minimum requirements: 256 MB RAM. ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Install it with the DaemonSet command Use kubectl (the Kubernetes command-line tool) to apply the kube-router-all-service-daemonset.yaml file. This starts one Kube-router process on each cluster node, so you get pod networking, service access, and firewall behavior without configuring every node by hand. source
  • Use the kubeadm file for kubeadm clusters If your cluster was built with kubeadm, set KUBECONFIG=/etc/kubernetes/admin.conf before running the kubeadm kubectl apply command. That tells kubectl where your admin credentials are and installs the network setup for pods to communicate and for network policies to work. source
  • Save the CNI config on each node Download 10-kuberouter.conf into /etc/cni/net.d/ on the node so Kubernetes can find it. Without this file, newly created pods may not get the network configuration they need to talk to each other. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Can kube-proxy run as a pod and still update iptables rules?

Yes, it can run as a Pod and still run iptables commands because it typically uses the host network namespace.

Where should I check kube-proxy logs when service traffic stops?

Check /var/log/kube-proxy.log, which contains logs from the kube-proxy process that directs traffic to Service endpoints.

Do I need to install kube-proxy in every Kubernetes setup?

It is necessary in some Kubernetes setups, while eBPF-based CNI projects such as Cilium can replace it.

Answers sourced from discuss.kubernetes.io, kubernetes.io, stackoverflow.com

Community

Collected 48 days ago - public community threads