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

Added Example to exclude Destination CIDRs from Egress Gateway #933

Merged
merged 1 commit into from
Aug 11, 2023

Conversation

M4t7e
Copy link
Contributor

@M4t7e M4t7e commented Aug 10, 2023

Cilium 1.14 adds support to exclude specific destination CIDRs (excludedCIDRs) from routing to the egress gateway. Just added this to the egress gateway policy example. Cilium has exceptions by default, but only for some "known" CIDRs/IPs. Everything else matching destinationCIDRs would be routed to the egress gateway.

See cilium/cilium#23448 and https://docs.cilium.io/en/stable/network/egress-gateway/#selecting-the-destination

Ping from Pod to LB without excludedCIDRs:

# ping 10.0.0.2 -c 5 -W 1
PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data.

--- 10.0.0.2 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 58ms

Ping from Pod to LB with excludedCIDRs:

# ping 10.0.0.2 -c 5 -W 1
PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data.
64 bytes from 10.0.0.2: icmp_seq=1 ttl=62 time=0.451 ms
64 bytes from 10.0.0.2: icmp_seq=2 ttl=62 time=0.466 ms
64 bytes from 10.0.0.2: icmp_seq=3 ttl=62 time=0.418 ms
64 bytes from 10.0.0.2: icmp_seq=4 ttl=62 time=0.417 ms
64 bytes from 10.0.0.2: icmp_seq=5 ttl=62 time=0.662 ms

--- 10.0.0.2 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 60ms
rtt min/avg/max/mdev = 0.417/0.482/0.662/0.095 ms

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.

Wonderful! Merging right away.

@mysticaltech mysticaltech merged commit 746ada7 into kube-hetzner:staging Aug 11, 2023
1 check passed
@mysticaltech
Copy link
Collaborator

@M4t7e Got shipped to master directly, no need for a release on that one as just the README 🙏

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.

2 participants