Kai Burjack

@primeroz , @hanxiaop : Both tickets (this one and https://github.com/istio/istio/issues/48326) got now auto-closed because it did not receive any updates from Istio team members. I was surprised at first sight...

@myoung34 [The `ignoreDifferences` spec field of the ArgoCD Application](https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/application.yaml#L212) is not meant to contain a YAML multiline *string* literal, but a structured YAML array/list. The workaround still works for me...

Thanks for the response! I am honing in on the actual issue (or rather the value override that caused it, I think). That means, the following works perfectly without any...

It's definitely caused by _some_ Helm value override in this (which we had been using successfully so far with Istio 1.21.2): ```yaml sidecarInjectorWebhook: enableNamespacesByDefault: true meshConfig: accessLogFormat: | { "authority":...

Okay, I am sorry, now I cannot reproduce my last case anymore, myself. I need to investigate more and find a 100% reproducible example first.

Okay, I got it. It is *this* Helm values override: ```yaml istio_cni: enabled: false pilot: cni: false #

Oh... and it was at this moment, that I realized, that it probably should have been: ```yaml pilot: cni: enabled: false ``` and not _just_: ```yaml pilot: cni: false ```...

Yepp... That was it... oh my god... :) Sorry, for all the confusion.

The Egress Gateway is _definitely_ terminating the TLS connection. I see the Common Name of the certificate (which we set to a distinct own name) when I do e.g. `curl...

> 1 request to a gateway generates 1 single metric, not a distinct one for upstream and downstream. Oh, that makes _total_ sense, since there is only one listener filter...