Replies: 2 comments 1 reply
-
@haircommander please suggest |
Beta Was this translation helpful? Give feedback.
0 replies
-
We directly enter the network namespace of the pod and forward the data: cri-o/internal/oci/runtime_oci_linux.go Lines 24 to 97 in e4975d5
I don't think so. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The Docker engine provides two mechanisms for forwarding ports from the host to containers, hairpin NAT, and the use of a userland proxy. In most circumstances, the hairpin NAT mode is preferred as it improves performance and makes use of native Linux iptables functionality instead of using an additional component.
How does port forwarding work in CRI-O?
Do we need to disable something similar in CRI-O as well?
Beta Was this translation helpful? Give feedback.
All reactions