How to config kong grpc healthcheck?

[kanbo]

Is there an existing issue for this?

• I have searched the existing issues

Kong version ($ kong version)

Kong 3.2.2

Current Behavior

error.log

2024/07/04 11:50:05 [error] 28965#0: *598 [lua] handler.lua:665: declarative reconfigure failed after 38 ms on worker #1: /usr/local/share/lua/5.1/resty/healthcheck.lua:1490: checks.active.type can only be 'http', 'https' or 'tcp', got 'grpc', context: ngx.timer

kong declarative_config :

services:
- name: grpc_test
  host: grpc_test
  connect_timeout: 10000
  protocol: grpc
  routes:
  - strip_path: true
    path_handling: v0
    preserve_host: true
    name: grpc_test
    hosts:
    - 10.16.156.231
    methods:
    - GET
    - POST
    paths:
    - /

upstreams:
- name: grpc_test
  algorithm: round-robin
  hash_on: none
  healthchecks:
    active:
      https_verify_certificate: false
      type: grpc
      http_path: /
      timeout: 3
      concurrency: 10
      healthy:
        successes: 3
        interval: 10
      unhealthy:
        tcp_failures: 3
        timeouts: 3
        http_failures: 3
        interval: 10

Expected Behavior

No response

Steps To Reproduce

No response

Anything else?

No response

[hanshuebner]

Kong Gateway only supports the http, https and tcp protocols for healthchecks. The configuration schema also allows grpc and grpcs to be specified, but those protocols are not actually supported. The lua-resty-healthcheck library provides the healthchecking implementation, please feel free to open a pull request to add grpc and grpcs support to that library.

[kanbo]

Kong Gateway only supports the http, https and tcp protocols for healthchecks. The configuration schema also allows grpc and grpcs to be specified, but those protocols are not actually supported. The lua-resty-healthcheck library provides the healthchecking implementation, please feel free to open a pull request to add grpc and grpcs support to that library.

Thank you. Is there any other way to solve this problem

[hanshuebner]

At this point, I can think of no solution to this problem. I will open an internal ticket to remind us that it exists and should eventually be fixed, although we can't give you a completion date. Again, if this feature is important to you, feel free to open a PR with a fix.

Internal ticket: KAG-4871

[hanshuebner]

@kanbo I'm converting this back to an issue as it really is a bug, not a feature request.