> Won't this forwarding/proxying make the internal services not see the actual source IP addresses making access logs less useful? Not when forwarding. When p

> Won't this forwarding/proxying make the internal services not see the actual source IP addresses making access logs less useful? Not when forwarding. When port forwarding using DNAT only, the internal container or VM service sees the remote IP address. As you say, HTTP has X-Forwarded-For. Because it is common to have one or more stages of HTTP reverse proxying these days for Internet-facing services for robustness (for example NginX proxy -> Python application), you'll probably have X-Forwarded-For configured already.