Skip to content

Conversation

pippolo84
Copy link
Member

The proxy rules installed by the iptables manager are the same regardless of the traffic direction (ingress or egress). So, there is no point in having separate functions to install them, nor passing a boolean flag indicating the traffic direction of the proxy.

The relevant interfaces and mock implementations are updated accordingly.

@pippolo84 pippolo84 added release-note/misc This PR makes changes that have no direct user impact. area/iptables Impacts how Cilium interacts with iptables. labels Feb 29, 2024
@pippolo84

This comment was marked as outdated.

@pippolo84 pippolo84 force-pushed the pr/pippolo84/iptables-proxy-rules branch from ccdaf55 to d24fac8 Compare February 29, 2024 17:14
@pippolo84

This comment was marked as outdated.

@pippolo84 pippolo84 force-pushed the pr/pippolo84/iptables-proxy-rules branch from d24fac8 to 970fc1a Compare February 29, 2024 17:25
@pippolo84
Copy link
Member Author

/test

@pippolo84 pippolo84 marked this pull request as ready for review February 29, 2024 18:22
@pippolo84 pippolo84 requested review from a team as code owners February 29, 2024 18:22
@pippolo84
Copy link
Member Author

Gentle ping to @tommyp1ckles for the review 🙏

The proxy rules installed by the iptables manager are the same
regardless of the traffic direction (ingress or egress). So, there is no
point in having separate functions to install them, nor passing a
boolean flag indicating the traffic direction of the proxy.

Signed-off-by: Fabio Falzoi <fabio.falzoi@isovalent.com>
The exported iptables manager method that allows to install the rules
needed to redirect traffic to a proxy requires a flag to specify the
proxy traffic direction.

Since the installed rules do not depend on the traffic direction, there
is no need to require that flag in the InstallProxyRules method
signature.

The relevant interfaces and mock implementations are updated
accordingly.

Signed-off-by: Fabio Falzoi <fabio.falzoi@isovalent.com>
@pippolo84 pippolo84 force-pushed the pr/pippolo84/iptables-proxy-rules branch from 970fc1a to 8c137f3 Compare March 18, 2024 18:02
@pippolo84
Copy link
Member Author

/test

@maintainer-s-little-helper maintainer-s-little-helper bot added the ready-to-merge This PR has passed all tests and received consensus from code owners to merge. label Mar 18, 2024
@julianwiedmann julianwiedmann added this pull request to the merge queue Mar 19, 2024
Merged via the queue into cilium:main with commit f2296eb Mar 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/iptables Impacts how Cilium interacts with iptables. ready-to-merge This PR has passed all tests and received consensus from code owners to merge. release-note/misc This PR makes changes that have no direct user impact.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants