Skip to content

Instantly share code, notes, and snippets.

Show Gist options
  • Save kubopanda/2e79d2544ccb08dcb7ed8ec281275cb6 to your computer and use it in GitHub Desktop.
Save kubopanda/2e79d2544ccb08dcb7ed8ec281275cb6 to your computer and use it in GitHub Desktop.
Q & A from Traefik Online Meetup: Maesh, a Simpler Service Maesh. Presented by The Traefik Team!

Q & A from Traefik Online Meetup: Maesh, a Simpler Service Maesh. Presented by The Traefik Team!

Check out the YouTube video: https://youtu.be/m-S8YZVwkfg

Question: Does Maesh handle SSL between services?

Answer: Maesh does not currently handle TLS/SSL between services. However, if your service implements TLS, a TCP connection through maesh will allow this to function properly. Full discussion: traefik/mesh#213

Question: When using Maesh to connect to other pods, does it use end to end SSL/TLS?

Answer: Not yet, see issue in question above.

Question: Is there any possibility to make Maesh work with Nomad instead of Kubernetes?

Answer: Currently, we are relying on some Kubernetesbased solutions (e.g. coreDNS), but we are evaluation the possibility to extend and make Maesh work on other platforms as well.

Question: Does Maesh add a unique http header for aggregation?

Answer: Currently, Maesh does not have custom header addition/modification functionality, however features can be requested on our Github project page.

Question: How does the mesh domain name get generated, which gets appended to the service name?

Answer: Maesh builds its endpoints via the following pattern: ..maesh

Note that the service namespace is required.

Question: The only immediate feedback/question I can think of, is the TLS between services would be great to have. For a lot of us this could be a show stopper, a lot of clients want TLS everywhere.

Answer: See github issue from above. Happy to have all your feedback!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment