Grpc expose - kubernetes GKE - kong 2.0.2

#1

Hi,

I deployed all-in-one-dbless - kong 2.0.2 on GKE.
any I’m trying to expose 2 different grpcs services with different paths.
for example :

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
name: grpcbin
spec:
rules:

  • http:
    paths:
    • path: /grpcbin/
      backend:
      serviceName: grpcbin-one
      servicePort: 9001

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
name: grpcbin2
spec:
rules:

  • http:
    paths:
    • path: /grpcbin2/
      backend:
      serviceName: grpcbin-two
      servicePort: 9001

but also when I’m trying to run the grpcurl command I’m getting an error:
grpcurl -v -d ‘{“greeting”: “Kong 1.3!”}’ -H ‘kong-debug: 1’ -insecure $PROXY_IP:443/grpcbin hello.HelloService.SayHello

Failed to dial target host “IP:443/grpcbin”: dial tcp: lookup tcp/443/grpcbin: nodename nor servname provided, or not known

Thanks!

#2

Please make sure Kong is accessible on the network first. The error you are getting is a likely a DNS resolution error.

#3

Hi,
The error is when I’m trying to set the path on the grpc service like:
“/grpcbin2/” or “/grpcbin/”
instead of “/” (root path)