Manuel Zapf

correct @Letme. And if you want to raise a PR to fix that, you're very welcome 👼

That looks fairly fine to build. You wanna give it a go @rektide ?

Personal opinion: I think having both would be very cool. A dashboard would obviously very cool, to have a quick spot to check about what is deployed where, current routes...

Im not too sure, if you can use the Dashboard like that with API insecure. Try without api insecure plx :)

@imdhruva what is your wanted outcome? Like how do you want the dashboard to have accessible? From what I see, you want to have it accessible via *http://traefikv2.test./dashboard/*. For that...

Hello @valerauko, thanks for your interest in the project. I'm not sure Maesh can handle that request tough. As we're non invassive, we don't have control over all outgoing connections....

I actually gave thoughts about that yesterday evening as well, and I think Port could be a good add (also for the UDP Spec). I think it's fine to have...

Another thought, just something that came to my mind. I know, initially has been said that it could be fine to avoid protocol detection. If we do want to have...

```yaml --- apiVersion: specs.smi-spec.io/v1alpha3 kind: TCPRoute metadata: name: mongo-routes namespace: default spec: matches: ports: - 27017 - 27018 - 27019 sni: host: my-mongo.cluster.svc.local --- kind: TrafficTarget metadata: name: tcp-demo namespace:...

SGTM @stefanprodan. Will take a look at #185 too