Matthias De Block

Hi @mateiidavid I did set 'bpf-lb-sock-hostns-only: "true"' but that did not fix the issue here. Without linkerd-cni everything is working fine.

> If you think linkerd-cni is the culprit, I'd suggest having a look at some logs. Specifically: > > * Does the installer (linkerd-cni daemonset pod) report anything? > *...

Hi Sorry for the delay, we will be testing again in the upcoming days. Regards Matthias

Hi As our cluster is air-gapped I noticed the 1.1.1.1 as connection address isn't correct. I've fixed this in our helm chart and we are now getting a bit further...

> Thanks @matthiasdeblock for circling back. With version 2.14.9 we have added a cni-repair-controller component that should detect race conditions between the cluster's cni and linkerd-cni. You can enable it...

Hi I have tested the image you provided but it still throws me the same error: ``` flatcar-k8stest-master-01 ~ # kubectl -n linkerd logs linkerd-destination-6c49f479d8-946ww -c linkerd-network-validator 2024-04-19T09:51:52.016640Z INFO linkerd_network_validator:...

@mateiidavid , any news on this one?

Hi The id token does have the groups information. Our other apps, for example Argocd, are working with the groups in the id token. They receive the groups as they...

Hi @mateiidavid Any news on this one? I have changed the timeout from 10s to 60s and now I am getting a different error: ``` flatcar-k8stest-master-01 ~ # kubectl -n...

Hi I have changed linkerd to the latest edge-24.5.5 and CNI to 1.5.0. Also have been putting the timeout to 30s. Still the same issue: ``` flatcar-k8stest-master-01 ~ # kubectl...