Draft: How kube-proxy Actually Routes a Packet: iptables vs IPVS vs eBPF#50
Draft
singhsanjay12 wants to merge 1 commit into
Draft
Draft: How kube-proxy Actually Routes a Packet: iptables vs IPVS vs eBPF#50singhsanjay12 wants to merge 1 commit into
singhsanjay12 wants to merge 1 commit into
Conversation
…IPVS vs eBPF Placeholder publish date (2026-05-04); adjust before publishing. Cross-links only to already-merged posts. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Draft blog post for review (merge later).
A ClusterIP is a virtual IP that nothing actually listens on. kube-proxy programs the kernel to rewrite it into a real pod, and the way it does that (iptables, IPVS, or eBPF) decides how your cluster behaves at scale.
🤖 Generated with Claude Code