Jef Spaleta

Hmm I'm having a really hard time figuring out where in the codebase the CiliumEndpoint created as part of CiliumExternalWorkload bring up is actually performed. The only call to the...

@sjm42 yeah there's a bug somewhere internal. I need to document a little more that I discovered with input from @joestringer to diagnos it a little further. the metadata that...

(Updated) I originally reported this as a regression relative to 1.14.10... that's wrong clean retests on 1.14.10 and I'm getting consistent behavior with tests on 1.15.4 and 1.15.5 Summary of...

Okay to reproduce the problem using the `imperial-gateway-native-routing` environment in my demos repo: First I edit the cilium helm values under `cilium/` directory and enable `bpf.masquerade` Then I provision the...

quick check and gateway has same issue, can't access via clusterIP from the same node. I'm able to see a difference between my tie and xwing pods only because i...

enabling bpf.legacyHostRouting did not help the situation. trying to curl the clusterIP of the deathstar ingress service from a pod on the same node as the deathstar backend pod still...

@sayboras definitely looks similar to the error in the "new" connectivity test. I'm using latest cilium-cli release 0.16.7, looks like that test is available ### running baseline native routing without...

just tested with 1.15.5 release, out today.. and still not working for me...even with the legacyHostRouting option enabled... ``` $ cilium version cilium-cli: v0.16.7 compiled with go1.22.2 on linux/amd64 cilium...

So not sure what is going on here. Kitch tests are timing out on this branch, it's not clear why.

let me take a look at this and see if I can figure it out. Ping here again on Monday if you haven't seen a response from me.