[SOLVED] How to using kubernetes traefik proxy grpc

Traefik Traefik v2
1

traefik proxy grpc 500 error

traefik version: v2.4.8
kubernetes version: v1.17.9
test grpc code: grpc-go/examples/helloworld/greeter_server at master · grpc/grpc-go · GitHub

ingress.yaml

# ingress
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: go-grpc-demo
  namespace: project-go-grpc-demo
  annotations:
    traefik.ingress.kubernetes.io/router.middlewares: "traefik-v2-autodetect@kubernetescrd"
    kubernetes.io/ingress.class: grpc
    # other annotations
    traefik.ingress.kubernetes.io/service.serversscheme: h2c
spec:
  rules:
  - http:
      paths:
      - path: /
        backend:
          serviceName: go-grpc-demo
          servicePort: http
    host: grpc.example.com

dashboards http services:

image
image940×365 21.4 KB

test project svc address normal.

test domain status code 500

* Rebuilt URL to: https://grpc.deeproute.cn/
*   Trying 10.9.9.133...
* TCP_NODELAY set
* Connected to grpc.deeproute.cn (10.9.9.133) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS Unknown, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, Unknown (8):
* TLSv1.3 (IN), TLS Unknown, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS Unknown, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS Unknown, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Client hello (1):
* TLSv1.3 (OUT), TLS Unknown, Certificate Status (22):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_CHACHA20_POLY1305_SHA256
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=deeproute.ai
*  start date: Mar 28 01:52:05 2021 GMT
*  expire date: Jun 26 01:52:05 2021 GMT
*  issuer: C=US; O=Let's Encrypt; CN=R3
*  SSL certificate verify result: unable to get local issuer certificate (20), continuing anyway.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* TLSv1.3 (OUT), TLS Unknown, Unknown (23):
* TLSv1.3 (OUT), TLS Unknown, Unknown (23):
* TLSv1.3 (OUT), TLS Unknown, Unknown (23):
* Using Stream ID: 1 (easy handle 0x55a6c1e14600)
* TLSv1.3 (OUT), TLS Unknown, Unknown (23):
> HEAD / HTTP/2
> Host: grpc.deeproute.cn
> User-Agent: curl/7.58.0
> Accept: */*
> 
* TLSv1.3 (IN), TLS Unknown, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS Unknown, Unknown (23):
* Connection state changed (MAX_CONCURRENT_STREAMS updated)!
* TLSv1.3 (OUT), TLS Unknown, Unknown (23):
* TLSv1.3 (IN), TLS Unknown, Unknown (23):
* TLSv1.3 (IN), TLS Unknown, Unknown (23):
* TLSv1.3 (IN), TLS Unknown, Unknown (23):
< HTTP/2 500 
HTTP/2 500 
< content-length: 21
content-length: 21
< date: Thu, 29 Apr 2021 04:23:07 GMT
date: Thu, 29 Apr 2021 04:23:07 GMT

< 
* Connection #0 to host grpc.deeproute.cn left intact
2

solve, need grpc client test,I using curl test url is error method

3

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.