run waypoint in consul service mesh #4905
Description
Is your feature request related to a problem? Please describe.
In the current waypoint version v0.11.4 there seems to be no way of running the waypoint-server with a gRPC port without TLS.
The issue we are facing is that we run the waypoint-server on Nomad connected to our Consul service mesh. This doesn't allow us to connect to it with the CLI because the sidecar terminates the TLS connection and then there is no option of configuring Envoy to talk to the service with TLS.
Describe the solution you'd like
Preferred solution would be to be able to configure the waypoint-server in a way that I can decide if the gRPC port should be TLS encrypted or not. When it is running in a service mesh I have a sidecar that takes care of TLS and don't want the service itself to do it.
Describe alternatives you've considered
I have tried to configure the sidecar to use TLS when talking to the service but from the documentation I understand that it will still talk TCP without TLS to the service: https://developer.hashicorp.com/consul/docs/connect/proxies/envoy#http2
Additional context
I managed to work around it and start a post-start task on nomad that configures the CLI and uses a static port to talk to the waypoint-server. That at least lets me semi-automate some setup bits. However, it breaks basically breaks the mesh as I circumvent the sidecar.