Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introducing Cilium 1.15.1 and Full kube-proxy Replacement #1222

Merged
merged 1 commit into from
Feb 23, 2024

Conversation

M4t7e
Copy link
Contributor

@M4t7e M4t7e commented Feb 22, 2024

This PR introduces Cilium 1.15.1, which supports Kubernetes versions 1.26, 1.27, 1.28, and 1.29.

This will also fix #1210 (#1199). Before this change, Cilium could only run in hybrid kube-proxy replacement mode. Now, full replacement is possible with the newly introduced disable_kube_proxy flag.

Another improvement is the bypassing of iptables connection tracking for Pod traffic in Cilium. This is only effective in native routing mode (cilium_routing_mode = "native").

For the case when eBPF Host-Routing cannot be used and thus network packets still need to traverse the regular network stack in the host namespace, iptables can add a significant cost. This traversal cost can be minimized by disabling the connection tracking requirement for all Pod traffic, thus bypassing the iptables connection tracker.

Copy link
Collaborator

@mysticaltech mysticaltech left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Simple and neat, yet extra powerful! You are a gem @M4t7e 🙏

@mysticaltech mysticaltech merged commit 98d933d into kube-hetzner:master Feb 23, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Cilium] Full Kube proxy replacement not working
2 participants