Grpc traffic broken, shows HTTP/2.0 on client proxy and HTTP/1.1 on server proxy

I have two services which speak grpc. When the request hits the client proxy it is logged as HTTP/2.0 but when the request hits the server proxy it is logged as HTTP/1.1. Consequently when the response is parsed by the client a parsing related exception is thrown. What is going on here?

Client Proxy
[2019-11-11T15:40:03.862Z] "POST /ai.argo.viaduct.proto.v1.ViaductAPI/Query HTTP/2" 200 - "-" "-" 1241 1280 405 405 "-" "grpc-java-netty/1.21.1" "2ef9594f-c22b-9e49-8d87-de76783f5439" "192.168.192.5:8085" "192.168.192.5:8085" PassthroughCluster - 192.168.192.5:8085 192.168.192.11:50252 -

Server Proxy

[2019-11-11T15:40:03.863Z] "POST /ai.argo.viaduct.proto.v1.ViaductAPI/Query HTTP/1.1" 200 - "-" "-" 1241 1280 405 404 "-" "grpc-java-netty/1.21.1" "2ef9594f-c22b-9e49-8d87-de76783f5439" "192.168.192.5:8085" "127.0.0.1:8085" inbound|8085|grpc-viaduct|viaduct.overwatch-development.svc.cluster.local - 192.168.192.5:8085 192.168.192.11:50230 -

Service Description

Name:                     viaduct
Namespace:                overwatch-development
Labels:                   <none>
Annotations:              external-dns.alpha.kubernetes.io/hostname: viaduct.dev.overwatch.argo.tools.
                          kubectl.kubernetes.io/last-applied-configuration:
                            {"apiVersion":"v1","kind":"Service","metadata":{"annotations":{"external-dns.alpha.kubernetes.io/hostname":"viaduct.dev.overwatch.argo.too...
                          service.beta.kubernetes.io/aws-load-balancer-backend-protocol: tcp
                          service.beta.kubernetes.io/aws-load-balancer-internal: 0.0.0.0/0
Selector:                 app=viaduct
Type:                     LoadBalancer
IP:                       172.20.86.120
LoadBalancer Ingress:     internal-a00aa67cec47111e9ac750a2cc3eb559-1876607380.us-east-1.elb.amazonaws.com
Port:                     tcp  8914/TCP
TargetPort:               rs/TCP
NodePort:                 tcp  31717/TCP
Endpoints:                192.168.128.3:8914,192.168.192.5:8914
Port:                     tls  443/TCP
TargetPort:               secure-rs/TCP
NodePort:                 tls  31490/TCP
Endpoints:                192.168.128.3:443,192.168.192.5:443
Port:                     grpc-viaduct  8085/TCP
TargetPort:               grpc/TCP
NodePort:                 grpc-viaduct  30266/TCP
Endpoints:                192.168.128.3:8085,192.168.192.5:8085
Session Affinity:         None
External Traffic Policy:  Cluster
Events:
  Type    Reason                Age                 From                Message
  ----    ------                ----                ----                -------
  Normal  EnsuringLoadBalancer  16m (x22 over 30d)  service-controller  Ensuring load balancer
  Normal  EnsuredLoadBalancer   16m (x22 over 30d)  service-controller  Ensured load balancer