gRPC Examples

Static configuration:

  web:
    address: :80
providers:
  file:
    directory: /path/to/dynamic/config
api: {}

--entryPoints.web.address=:80
--providers.file.directory=/path/to/dynamic/config
--api.insecure=true

/path/to/dynamic/config/dynamic_conf.{toml,yml}:

## dynamic configuration ##
[http]
  [http.routers]
    [http.routers.routerTest]
      service = "srv-grpc"
      rule = "Host(`frontend.local`)"
  [http.services]
    [http.services.srv-grpc]
      [http.services.srv-grpc.loadBalancer]
        [[http.services.srv-grpc.loadBalancer.servers]]
          url = "h2c://backend.local:8080"

## dynamic configuration ##
http:
  routers:
    routerTest:
      service: srv-grpc
      rule: Host(`frontend.local`)
  services:
      loadBalancer:
        servers:
        - url: h2c://backend.local:8080

Warning

For providers with labels, you will have to specify the traefik.http.services..loadbalancer.server.scheme=h2c

Conclusion

We don't need specific configuration to use gRPC in Traefik, we just need to use h2c protocol, or use HTTPS communications to have HTTP2 with the backend.

With HTTPS

This section explains how to use Traefik as reverse proxy for gRPC application with self-signed certificates.

In order to secure the gRPC server, we generate a self-signed certificate for service url:

That will prompt for information, the important answer is:

Common Name (e.g. server FQDN or YOUR name) []: backend.local

gRPC Client Certificate

Generate your self-signed certificate for router url:

with

Common Name (e.g. server FQDN or YOUR name) []: frontend.local

At last, we configure our Traefik instance to use both self-signed certificates.

Static configuration:

[entryPoints]
  [entryPoints.websecure]
    address = ":4443"
[serversTransport]
  # For secure connection on backend.local
  rootCAs = [ "./backend.cert" ]
[api]
[provider.file]
  directory = "/path/to/dynamic/config"

--entryPoints.websecure.address=:4443
# For secure connection on backend.local
--serversTransport.rootCAs=./backend.cert
--providers.file.directory=/path/to/dynamic/config
--api.insecure=true

## dynamic configuration ##
[http]
  [http.routers]
    [http.routers.routerTest]
      service = "srv-grpc"
      rule = "Host(`frontend.local`)"
  [http.services]
    [http.services.srv-grpc]
      [http.services.srv-grpc.loadBalancer]
        [[http.services.srv-grpc.loadBalancer.servers]]
          # Access on backend with HTTPS
          url = "https://backend.local:8080"
[tls]
  # For secure connection on frontend.local
    certFile = "./frontend.cert"
    keyFile = "./frontend.key"

http:
  routers:
    routerTest:
      service: srv-grpc
      rule: Host(`frontend.local`)
  services:
    srv-grpc:
      loadBalancer:
        servers:
        # Access on backend with HTTPS
        - url: https://backend.local:8080
tls:
  # For secure connection on frontend.local
  certificates:
  - certfile: ./frontend.cert
    keyfile: ./frontend.key

Warning

With some services, the server URLs use the IP, so you may need to configure insecureSkipVerify instead of the rootCAs to activate HTTPS without hostname verification.

A gRPC example in go (modify for https)

We use the gRPC greeter example in grpc-go

Warning

In order to use this gRPC example, we need to modify it to use HTTPS

So we modify the "gRPC server example" to use our own self-signed certificate:

// ...
// Read cert and key file
backendCert, _ := ioutil.ReadFile("./backend.cert")
backendKey, _ := ioutil.ReadFile("./backend.key")
// Generate Certificate struct
cert, err := tls.X509KeyPair(backendCert, backendKey)
if err != nil {
  log.Fatalf("failed to parse certificate: %v", err)
}
// Create credentials
creds := credentials.NewServerTLSFromCert(&cert)
// Use Credentials in gRPC server options
serverOption := grpc.Creds(creds)
var s *grpc.Server = grpc.NewServer(serverOption)
defer s.Stop()
pb.RegisterGreeterServer(s, &server{})
err := s.Serve(lis)