stream routing does not work in DB-less and hybrid mode

[hbagdi]

Summary

Stream routes are not propagated in DB-less mode and Kong always closes the TCP connections with an error log entry of no routes found. This works in DB-mode.

Steps To Reproduce

Populate Kong with following configuration:

_format_version: "1.1"
services:
- connect_timeout: 60000
  host: httpbin.org
  name: httpbin.httpbin.80
  port: 80
  protocol: tcp
  read_timeout: 60000
  retries: 5
  write_timeout: 60000
  routes:
  - name: httpbin.example-app1.0
    protocols:
    - tcp
    destinations:
    - port: 9000

telnet localhost 9000 will not work.

Run the same setup with postgres and that works.

Additional Details & Logs

• Kong version ($ kong version) 2.0.2
• Operating system: Docker

[braedon]

Any update on when this could be fixed? I just spent half a day trying to get streams set up, only to find this issue 😞

[kikito]

Unfortunately we won't be able to fix this until we are able to share memory between the http and stream subsystems, which is a limitation in Openresty at the moment. We have an open PR for Openresty with a fix in:

openresty/meta-lua-nginx-module#76

[dndx]

Note: According to my test (re)loading the declarative config using the Kong CLI works. It's the dynamic update at runtime using the /config endpoint not working. We are working on a fix right now.

[subnetmarco]

This is a blocker for Kuma as well.

[morningspace]

Just to be sure as I was looking for ssl passthrough solution using Kong ingress controller. It appears to me, this won't work because of this issue, right? Since Kong operator is based on DB-less mode Kong deployment, it's not possible to forward the HTTPs traffic as TCP stream to backend by using this feature. Please correct me if any. @hbagdi

[hbagdi]

It appears to me, this won't work because of this issue, right?

You can also use Kong Ingress Controller with a database. This bug doesn't affect Kong with a database.