[英]How traffic routing happens in Kubernetes operator - Journey of Egress traffic
I am trying to understand about egress traffic controlling inKubernetes-Operator .我试图了解Kubernetes-Operator 中的出口流量控制。 If I implement Kubernetes operator in my k3s setup, how the egress traffic flow happens in the operator?如果我在 k3s 设置中实现了 Kubernetes 操作符,那么该操作符中的出口流量是如何发生的?
I want to understand that what pathway/gateway and routing happens with egress traffic flow happens in the Kubernetes operator (journey of egress traffic)?我想了解在 Kubernetes 运营商(出口流量之旅)中,出口流量发生了什么路径/网关和路由?
As a general rule, egress traffic leaves your SDN from the Node hosting your Pod.作为一般规则,出口流量会从托管您的 Pod 的节点离开您的 SDN。 The Node would NAT it, using its own IP on your underlay network.节点将使用它自己的 IP 在您的底层网络上对其进行 NAT。
Now, if by Egress you mean "anything that leaves my Pod" / regarding communications that stay within the SDN.现在,如果 Egress 是指“离开我的 Pod 的任何东西”/关于留在 SDN 内的通信。 Bearing in mind that:铭记:
Connecting a Service, the Node firewall (usually ipvs or iptables, as configured per kube-proxy) would redirect your connection one of the addresses listed in the corresponding Endpoint object.连接服务时,节点防火墙(通常是 ipvs 或 iptables,根据 kube-proxy 的配置)会将您的连接重定向到相应端点对象中列出的地址之一。 At which point, your Node routing table takes over:此时,您的节点路由表将接管:
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.