# kube-proxy

kube-proxy is a network proxy that runs on every node of a Kubernetes cluster. It is open source and self-hosted, installable on Docker Hub and Kubernetes (Helm).

Canonical page: https://ourlocalhost.com/app/6048/kube-proxy

## Description

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: Helm.

## Health score

74/100 (Good), based on 5 of 5 factors.
- Maintained: 100 (last commit 17 days ago)
- Popular: 47 (214 GitHub stars)
- Easy to install: 35 (1 install platform, install notes, Docker image)
- Light to run: 100 (256 MB minimum RAM, runs on ARM)
- Security check: 75 (no serious findings, tests, OpenSSF Scorecard 5.3/10)

## Links

- GitHub: https://github.com/kubernetes/kube-proxy
- Docker Hub: https://hub.docker.com/r/cleanstart/kube-proxy
- Kubernetes (Helm): https://artifacthub.io/packages/helm/stevehipwell/kube-proxy

## 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.

---
Source: Our Local Host (https://ourlocalhost.com/app/6048/kube-proxy), the self-hosted and open-source app directory.
