Krzysztof Słonka

I [have a branch](https://github.com/kumahq/kuma/compare/master...slonka:kuma:fix-multiple-inbounds-mixup?expand=1) - still needs some work to reproduce this. Not sure if I'll have time to work on it, or the next on-duty will pick this up...

Tried reproducing this (on 2.6.0) using python and `http.server` like this: ```yaml apiVersion: apps/v1 kind: Deployment metadata: name: echo namespace: kuma-demo spec: replicas: 1 selector: matchLabels: app: echo template: metadata:...

Any updates on this?

Hi Andrew, Thanks for the update! 🙂 I was just wondering if this was actively worked on and if there is anything that can be split into smaller tasks so...

hi @andrewpollock - thank you very much for the update! Is this only available via the REST API or does it already work with [osv-scanner](https://github.com/google/osv-scanner)?

Bumping this and voting 👍 because we just spent some time with @bartsmykla trying to figure out outbound naming mistake.

@tomtomtomtom44 can you try https://kuma.io/docs/2.8.x/policies/meshpassthrough/#meshpassthrough and let us know what you think?

> Why? This results in an error log on our side ``` stream to execute Stats operations is not yet connected ```

> And it’s better to avoid this error at the cost of adding a new API call in the UI (calling /zones+insights so we know whether a Zone is online)?...

For now a user can click on the outbound:  click on clusters and associate pod ip with cluster ip: