azunna1

Using these annotations on the pod template fixes the issue - `sidecar.istio.io/rewriteAppHTTPProbers: 'false'`, `traffic.sidecar.istio.io/excludeInboundPorts: '9801'`. The problem is that the istio-validation init container always starts first. If you have strict...

For a more permanent fix, the csql sidecar containers should run as user `1337` as stated here: https://cloud.google.com/knowledge/kb/pod-are-fail-to-start-due-to-init-containers-not-starting-with-istio-cni-enabled-000007358 I tried using the AuthProxyWorkload's `AuthProxyWorkloadSpec` container field to set it but...

Hi @hessjcg just wanted to check for updates on this?

I believe to detect istio, you can check for the presence of some annotations in the pod such as `istio.io/rev` or labels such as `sidecar.istio.io/inject=true` and `service.istio.io/canonical-name`. Also istio sidecars...

Hi @hessjcg, would you like some assistance with this? My Golang is a bit rough but i could give this issue a try with some guidance. We use istio in...

Hi @bblackbelt With Istio, you need to ensure that you set a health check for your containers. Can you share the full pod/deployment yaml?

Try adding a liveness probe to the init container. It's the only difference i can see between my setup and yours. ``` livenessProbe: httpGet: path: /liveness port: 9801 scheme: HTTP...

@joran-fonjallaz @bblackbelt I tried again and realised that removing all the probes works fine. You still have to set the UID to `1337`. Unfortunately, the latest istio features are not...

This is why - https://github.com/grafana/loki/blob/d5b382b90738505d8bf7217ff3a1a8c90fc09b7e/pkg/querier/multi_tenant_querier.go#L321-L324 The Pull request to address this ([#17031](https://github.com/grafana/loki/pull/17031)) was never merged into the releases, i wonder why. @gtk-grafana Is this something you can help with?