You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
metadata: Eliminate separate 'ingress_source_identity'
Both debug logging and access logging are more intelligible when the
original source identity is used, also in the case of the north/south L7
LB, where an "Ingress IP" is used as the source address in the upstream
connections. In that case SO_MARK encodes the identity of the Ingress IP
so that the source identity seen in the destination is the same when the
destination is in the same node (source identity derived from SO_MARK)
and when the destination is in a different node (source identity mapped
from the source (Ingress) IP).
Note that the (original) source identity is used for policy determination
only for ingress policy, for which the original source identity was
already used. Given this, the only visible change is the source identity
as seen on debug/trace logs and (hubble) access logs. Access logs already
show the original source address, so this change aligns the recorded
source identity with it, so that instead of:
Jun 18 12:37:20.940: default/ubuntu-deployment-6f7cc4b9fb-9gmnp:39430 (ingress) -> default/nginx-deployment-worker-7d99874b8b-dw4bt:80 (ID:53552) http-request FORWARDED (HTTP/1.1 GET http://10.96.154.80/)
Hubble will show this:
Signed-off-by: Jarno Rajahalme <[email protected]>
0 commit comments