GRPC with kong.yaml and docker compose

Questions
1

So I have a docker compose with a grpc service called triton on 8001, and a kong dbless service.

This is my kong.yaml

services:
  - name: triton-grpc
    protocol: grpc
    host: triton
    port: 8001
    routes:
      - name: grpc
        protocols:
          - grpc
        paths:
          - /

This is my docker compose:

services:
  triton:
    user: triton-server
    image: nvcr.io/nvidia/tritonserver:24.07-py3
...
    ports:
      - "8000:8000" # HTTP
      - "8001:8001" # GRPC

  kong-dbless:
    image: kong:latest  # Use the specified Kong image version
    container_name: kong-dbless
    depends_on:
      - triton
...
    environment:
      - KONG_DATABASE=off  # Disable the database
      - KONG_DECLARATIVE_CONFIG=/kong/kong.yaml  # Specify the declarative config file
      - KONG_PROXY_ACCESS_LOG=/dev/stdout  # Log proxy access to stdout
      - KONG_ADMIN_ACCESS_LOG=/dev/stdout  # Log admin access to stdout
      - KONG_PROXY_ERROR_LOG=/dev/stderr  # Log proxy errors to stderr
      - KONG_ADMIN_ERROR_LOG=/dev/stderr  # Log admin errors to stderr
      - KONG_PROXY_LISTEN="0.0.0.0:8000 reuseport backlog=16384, 0.0.0.0:8443 http2 ssl reuseport backlog=16384, 0.0.0.0:9080 http2 reuseport backlog=16384, 0.0.0.0:9081 ssl http2 reuseport backlog=16384"
    ports:
      - 80:8000  # http
      - 443:443  # https
      - 9080:9080 # grpc
      - 9081:9081 # grpc ssl

I am not sure if I need the KONG PROXY LISTEN or what I need to set there to turn on grpc. If I call my triton service direct via grpc it works. But when I call it via Kong it doesn’t work. Not sure how to get this working…

2

@jungle Can you provide error messages either on requests made to Kong Gateway or within the Kong Gateway logging?