Skip to content

Commit

Permalink
docs: Clarify LRP loop related note
Browse files Browse the repository at this point in the history
The previous document note can lead to confusion for readers, whereby
its misinterpreted as node-local translation being skipped, but regular translation
can happen. Clarify how we avoid forming a loop by rewording the note.

Signed-off-by: Aditi Ghag <aditi@cilium.io>
  • Loading branch information
aditighag authored and nathanjsweet committed Jun 2, 2021
1 parent 49267a5 commit 2783833
Showing 1 changed file with 5 additions and 3 deletions.
8 changes: 5 additions & 3 deletions Documentation/gettingstarted/local-redirect-policy.rst
Original file line number Diff line number Diff line change
Expand Up @@ -476,6 +476,8 @@ security credentials for pods.
Miscellaneous
=============
When a Local Redirect Policy is applied, cilium BPF datapath translates frontend
(ip/port/protocol tuple) from the policy to a node-local backend pod selected
by the policy. However, such translation is skipped using ``sk_lookup`` BPF
helpers for traffic that originates from the backend and is destined to the frontend .
(identified by ip/port/protocol tuple) address from the policy to a node-local backend
pod selected by the policy. However, when traffic originates from the node-local
backend pod(s), and is destined to the policy frontend, we skip translating the
frontend address using ``sk_lookup_`` BPF helpers. This is done in order to avoid
forming a loop. As a result, traffic in such cases is forwarded to the original frontend.

0 comments on commit 2783833

Please sign in to comment.