Radosław Piliszek

Hi @bblommers! I hope you are doing well. Is there any way I could help you with analysing this PR?

I hit the same issue on Talos Linux (https://www.talos.dev/) because of this security-by-default approach. The bottom line is - we are missing a way to specify liqo's namespaces' labels via...

Hi @cheina97 I see this issue is still present in the latest (v0.10.1) Liqo and happens when peering fails for any reason. In my case though, the uninstall fails trying...

FWIW, its namespace was already deleted...

**Workaround** All right, I recreated the namespace and then I was able to remove the finalizers (and had to also delete the invalid ownerReferences) and delete it. Oh boy, it...

Thanks for the summary @cheina97 and no need to be sorry! It works very fine so far except for these quirks. I have seen these various improvements being mentioned around...

> ``` > auth 2023/12/20 08:04:00 http: TLS handshake error from 10.0.0.199:3205: EOF > > ``` > > source addresses above are Cilium "routers" at nodes. That's because they open...

Hmm, but the docs for 1.6+ should not drop the instructions for configuring KubePrism as they are still very valid...

Confusing humans, maybe unnecessary extra work for machines. Low priority in general but something to fix in the long run IMHO.

This applies to the latest release as well. RECLAIMABLE is badly named.