Andrei Kvapil
Andrei Kvapil
@stevefan1999-personal try this: ``` helm template asd oci://ghcr.io/stefanprodan/charts/podinfo | grep Source ```
Now there is too many upgrades available 🙂 
This change is still desirable
/assign @qinqon
/retest
Not sure if it is somehow useful, but I just tried to do a trace: ``` ovn-trace --no-friendly-names --ovs 79ddba83-8e94-4b7e-ae2c-e15e88323208 'inport == "kubernetes-infra-md0-jvsx2-mf45n.tenant-root" && ip4.dst == 10.2.0.241' ``` Got this...
In ovn-sbctl dump-flows, I see my cluster-ip but don't see external-ip, maybe this is an issue? ``` root@srv2:/kube-ovn# ovn-sbctl dump-flows | grep 10.2.0.241 root@srv2:/kube-ovn# ovn-sbctl dump-flows | grep 10.96.181.254 table=6...
@zhangzujian could you please point me into right place in code where these rules for `cluster-ip` get created? I can investigate my time for adding `external-ip` support there as well.
> Kube-OVN adds an iptables rule for such traffic I guess packets do not reach host networking namespace due to fact I can see them only in `ovn0` interface and...
Did you tested VM or pod? It is working fine for me for ordinary pods, but not for the VMs