Describe the bug
antctl traceflow doesn't work for destination service.
The injected packet is not processed as packets to service(clusterip) in ovs pipeline.
Expected
The injected packet is loadbalanced and delivered to the pod.
Based on analysis with @gran-vmv , the following flag must be set to 2 when traffic is sent out to service.
transportHeader:
tcp:
srcPort: xx
dstPort: xx
flags: 2
Container runtime: which runtime are you using (e.g. containerd, cri-o, docker) and which version are you using?
Docker 19.0.3.4
Linux kernel version on the Kubernetes Nodes (uname -r).
4.15.0-112-generic
If you chose to compile the Open vSwitch kernel module manually instead of using the kernel module built into the Linux kernel, which version of the OVS kernel module are you using? Include the output of modinfo openvswitch for the Kubernetes Nodes.
Additional context
Add any other context about the problem here, such as Antrea logs, kubelet logs, etc.
(Please consider pasting long output into a GitHub gist or any other pastebin.)
Describe the bug antctl traceflow doesn't work for destination service.
The injected packet is not processed as packets to service(clusterip) in ovs pipeline.
To Reproduce Do antctl traceflow for traffic to service like below.
Expected The injected packet is loadbalanced and delivered to the pod. Based on analysis with @gran-vmv , the following flag must be set to 2 when traffic is sent out to service.
Then It should work like below.
Actual behavior The injected packet is not processed as packets to service(clusterip) in ovs pipeline.
Versions: Please provide the following information:
kubectl version
). If your Kubernetes components have different versions, please provide the version for all of them.uname -r
). 4.15.0-112-genericmodinfo openvswitch
for the Kubernetes Nodes.Additional context Add any other context about the problem here, such as Antrea logs, kubelet logs, etc.
(Please consider pasting long output into a GitHub gist or any other pastebin.)