VivekSubr

thank you @adisuissa, that works.

Looks like bazel rules_go queries golang.org if sdks aren't specified... https://github.com/bazelbuild/rules_go/blob/master/go/private/sdk.bzl Perhaps we are forced to specify sdks manually using [go_download_sdk](https://github.com/bazelbuild/rules_go/blob/master/go/toolchains.rst#go_download_sdk)?

@lalitb - sorry for the late reply, so your saying, something like `AddEvent("event", opentelemetry::common::SystemTimestamp(), "log") ` Would translate to key : value for jaeger? I'll try that and get back...

Also, I note that the cni test cases in istio/cni/test/install don't have one for this use case, mutiple CNIs using multus... do you how that might look like? What are...

@howardjohn @jwendell @jacob-delgado ... Hi, just one more question... I don't see this 15002 port in iptables rules of istio proxy ``` root@aks-worker-12986694-vmss000003 [ / ]# sudo nsenter -t 36148...

Hi @howardjohn, thanks for the reply... have one more question - so, I'm trying to debug istio-iptables for working and non-working cases, and I can see that there's an env...

@howardjohn - oh, okay... this there any way to enable logging for the istio-cni binary?

no, it's not... it's vanilla 1.16.3, and that too working case. In non working case, the pods don't come up hence can't take iptables dump, so I need to see...

@howardjohn, hi, so the root cause of this looks to be that operator or cni is not honoring the config 'chained=false'. In Operator, we configure, ``` values: cni: image: cniConfDir:...

@howardjohn @jacob-delgado Hi, root caused it. Looks to be a misconfiguration that was working, until changes introduced by: https://github.com/istio/istio/pull/45207 Before this, istio was injecting ' k8s.v1.cni.cncf.io/networks : istio-cni', but looks...