Kornilios Kourtis

> did you do some troubleshooting already? Not really, just the basic things (logs, etc.) but didn't notice anything relevant. > What does 'nodes unreachable' mean in this context? host->host...

Seems to also happen with latest 1.8. (to clarify, this is with vxlan.)

> @kkourt Also any hints on the environment would be helpful? Is this GKE, This is GCE, i.e., google VMs.

> @aanm @aditighag I managed to reproduce this on a fresh Ubuntu 22.04 installation and kubeadm. Here is the sysdump. [cilium-sysdump-20220613-221201.zip](https://github.com/cilium/cilium/files/8895759/cilium-sysdump-20220613-221201.zip) Thanks @weikinhuang! How did you created the sysdump? It...

> @kkourt, I just ran `cilium sysdump`. My cilium pods are running in the `cilium-cni` namespace instead of `kube-system`. Updated the sysdump with the extra namespace flags. > > [cilium-sysdump-20220616-083851.zip](https://github.com/cilium/cilium/files/8918870/cilium-sysdump-20220616-083851.zip)...

That's a good point! We do not have release management scheme yet, but we plan to do a minor release with all the updates since May soon.

Hi @andylibrian, This is not currently supported, but it is on our roadmap.

Yes. see: https://github.com/cilium/tetragon/blob/main/crds/examples/hardlink-override.yaml. Note also that there was a PR merged right now which allows to use the above from a CRD (https://github.com/cilium/tetragon/pull/424).

Thanks @tklauser! Regarding the test failure: https://github.com/cilium/tetragon/runs/6588057292: > > { > "process_kprobe": { > "process": { > "pid": 11522, > "start_time": "2022-05-25T08:03:04.685Z" > }, > "parent": {}, > "function_name": "__x64_sys_writev",...

Thank you for the report! Could you please add the logs from the tetragon container?