Saved in:
| Main Authors: | , , |
|---|---|
| Format: | Preprint |
| Published: |
2025
|
| Subjects: | |
| Online Access: | https://arxiv.org/abs/2505.05996 |
| Tags: |
Add Tag
No Tags, Be the first to tag this record!
|
| _version_ | 1866916728839077888 |
|---|---|
| author | Grigoryan, Garegin Penkowski, Kevin Kwon, Minseok |
| author_facet | Grigoryan, Garegin Penkowski, Kevin Kwon, Minseok |
| contents | Kubernetes Services such as LoadBalancer and NodePort expose applications running on pods within a Kubernetes cluster to external users. While the LoadBalancer Service requires an external load-balancing middleware, its alternative, NodePort Service, adds additional hops on the path between clients and the worker nodes. In this paper, we propose P4Kube, a framework consisting of a P4 data plane program and a Kubernetes plugin. Our solution effectively performs load balancing of requests to the worker nodes of a cluster based on the number of running replicas. In P4Kube, the data packets completely bypass the system's control plane. Unlike the previous work, to update its state, the P4Kube data plane works directly with the Kubernetes control plane without any involvement of the network control plane. Our experiments show up to 50% improvement in the average request time to the cluster compared to conventional approaches. |
| format | Preprint |
| id |
arxiv_https___arxiv_org_abs_2505_05996 |
| institution | arXiv |
| publishDate | 2025 |
| record_format | arxiv |
| spellingShingle | P4Kube: In-Network Load Balancer for Kubernetes Grigoryan, Garegin Penkowski, Kevin Kwon, Minseok Networking and Internet Architecture Kubernetes Services such as LoadBalancer and NodePort expose applications running on pods within a Kubernetes cluster to external users. While the LoadBalancer Service requires an external load-balancing middleware, its alternative, NodePort Service, adds additional hops on the path between clients and the worker nodes. In this paper, we propose P4Kube, a framework consisting of a P4 data plane program and a Kubernetes plugin. Our solution effectively performs load balancing of requests to the worker nodes of a cluster based on the number of running replicas. In P4Kube, the data packets completely bypass the system's control plane. Unlike the previous work, to update its state, the P4Kube data plane works directly with the Kubernetes control plane without any involvement of the network control plane. Our experiments show up to 50% improvement in the average request time to the cluster compared to conventional approaches. |
| title | P4Kube: In-Network Load Balancer for Kubernetes |
| topic | Networking and Internet Architecture |
| url | https://arxiv.org/abs/2505.05996 |