docs(MADR): MeshTCPRoute proposal

[bartsmykla]

Checklist prior to review

• Link to relevant issue as well as docs and UI issues
  • Closes Design MeshTCPRoute #6343
• This will not break child repos: it doesn't hardcode values (.e.g "kumahq" as a image registry) and it will work on Windows, system specific functions like syscall.Mkfifo have equivalent implementation on the other OS --
  • it won't as it's just a MADR
• Tests (Unit test, E2E tests, manual test on universal and k8s)
  • no tests as it's just a MADR
• Do you need to update UPGRADE.md?
  • no need as it's just a MADR
• Does it need to be backported according to the backporting policy?
  • no need as it's just a MADR
• Do you need to explicitly set a > Changelog: entry here or add a ci/ label to run fewer/more tests?
  • no

[lobkovilya]

I'd also mention the behavior with respect to the protocol. I guess it should not be possible to apply MeshTCPRoute for HTTP service

[bartsmykla]

Apologies for force pushing, but I made a mess with unfortunate rebase by mistake.

[lahabana]

One thing that isn't covered is what happens when both a TCP and an HTTP route match

[bartsmykla]

One thing that isn't covered is what happens when both a TCP and an HTTP route match

That's a good question. Let me figure this out, and update the MADR.

changed