Skip to content

CFP-12781: Host Firewall Before NodePort DNAT#97

Open
jakubhlavnicka wants to merge 2 commits into
cilium:mainfrom
jakubhlavnicka:cfp-12781-host-firewall-before-nodeport-dnat
Open

CFP-12781: Host Firewall Before NodePort DNAT#97
jakubhlavnicka wants to merge 2 commits into
cilium:mainfrom
jakubhlavnicka:cfp-12781-host-firewall-before-nodeport-dnat

Conversation

@jakubhlavnicka

Copy link
Copy Markdown

Add CFP for enforcing host firewall ingress policy before NodePort DNAT/SNAT, which enables CiliumClusterwideNetworkPolicy to match on original external source IPs and NodePort destination ports.

Tracks: cilium/cilium#12781

Signed-off-by: Jakub Hlavnicka <jakub.hlavnicka@illumio.com>
@joestringer

Copy link
Copy Markdown
Member

My gut feeling is this is not something we can add a flag for and reasonably continue maintaining and supporting. More likely we need to consider new API syntax to match the relevant hook point.

cc @cilium/sig-policy we discussed this during the most recent meeting.

@julianwiedmann julianwiedmann left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I'm not seeing any consideration for loadBalancerSourceRanges. Can you describe why it's not sufficient for your purposes?

Signed-off-by: Jakub Hlavnicka <jakub.hlavnicka@illumio.com>
@jakubhlavnicka

Copy link
Copy Markdown
Author

@julianwiedmann - I've added a section to the CFP addressing why loadBalancerSourceRanges is not sufficient for this use case: f3894a4

@joestringer - Thank you for the feedback. Are you suggesting a new policy API field on CiliumClusterwideNetworkPolicy, something like preSNATIngress with the same syntax as the existing ingress field, that would explicitly target the pre-SNAT hook point? Or rather an entirely new policy kind for this purpose?

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.

3 participants