Tomas Hruby comments

Results 150 comments of


                                            Tomas Hruby

v2 breaks the way --ginkgo.parallel.process -and -ginkgo.parallel.total used to work

Hey @onsi yeah I can see it is all ready for multi-worker setup :+1: > Would you rather import a library and write your own code to spin up a...

HostPort of pod/container can't access from other nodes in eBPF mode

@gongzh the solution is to set `FELIX_BPFHostConntrackBypass=false` You have to do it as an env variable for now as it is missing in the felix configuration resource. Will be fixed.

HostPort of pod/container can't access from other nodes in eBPF mode

@gongzh @seh heads up - this workaround would not work for 3.24+ . As we understand the issue now, there is in fact little guarantee that a packet will go...

HostPort of pod/container can't access from other nodes in eBPF mode

@seh right, we are looking into how to close the gap and we will most likely backport that too.

HostPort of pod/container can't access from other nodes in eBPF mode

The issue is fixed and should work as expected in v3.25

HostPort of pod/container can't access from other nodes in eBPF mode

@mazdakn could you backport it to 3.24 too? :pray:

K8s NodePort Service can only be accessed locally but not externally when using eBPF dataplane

I do not quite follow what is the problem. It seems like when you are trying to access the nodeport from either of the 2 k8s node, you get a...

K8s NodePort Service can only be accessed locally but not externally when using eBPF dataplane

Could you also set `BPFLogLevel` felix config to `Debug` and get us output from `tc exec bpf debug >& tc.log` on the node which you are trying to connect to?...

VM access was blocked when eBPF dataplane used

@TrevorTaoARM sorry for not responding sooner, totally missed this, :eyes: now! And thanks for a great analysis! :pray:

VM access was blocked when eBPF dataplane used

@TrevorTaoARM I commented at your patch :arrow_up: