Request goes through envoy and into the grpc service but the response doesn't come back

I have a working app that uses `grpc-web` via `app -> envoy -> grpc service` so far so good, but if I deploy the app to `gke` (Google Kubernetes Engine) and turn on TLS I start getting `2 UNKNOWN: No status received` replies.

I can see the request reaching the grpc service just fine and in turn the service replies, but the response is not reaching the app, and I'm extremely puzzled as I cannot see what could be going wrong, if this works without TLS perhaps the TLS is messing something?

Technically the deployed service looks like `app -> gke ingress + ssl -> envoy + tls -> service` note the addition of the google ingress controller which terminates SSL and then passes the request to envoy over TLS and in turn to the service, if things are going well as a request, what could be causing the response to go missing?

if my grpc service returns an error it does make it back

with BloomRPC I can see

```
{
"error": "3 INVALID_ARGUMENT: invalid credentials"
}
```

Any other response that is successful

```
{
"error": "2 UNKNOWN: No status received"
}
```

if I test with grpcurl I can see some trailers are "missing"

```
grpcurl -d @ -import-path protos -proto accounts.proto -vv mydomain:443 my.Service/Login <