Added Example to exclude Destination CIDRs from Egress Gateway #933
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.
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 matchingdestinationCIDRs
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 from Pod to LB with
excludedCIDRs
: