kong · Issues· 200 open

ai-proxy-advanced (llm_format: bedrock): 500 in bedrock adapter when a content block follows toolResult in the same message

worker.lua:164: failed to store event: queue overflow causes mlcache invalidation loss and stale upstream targets

PostgreSQL TLS handshake omits SNI, breaking Kong behind SNI-routing proxies (bundled pgmoon passes nil server_name)

rate-limiting: Redis keys have wrong TTL when `sync_rate > 0`

Kong DNS resolver silently drops all options when /etc/resolv.conf has multiple options on a single "options" line (breaks Kubernetes dnsConfig)

Is KONG community dead ? Will there ever be a new release made for OSS / CE ?

ai-prompt-decorator re-encodes empty JSON arrays as objects (tools: [] → tools: {})

pg_ssl_cert / pg_ssl_cert_key are documented but silently ignored in Kong Gateway OSS

Kong's internal DNS client fails to resolve a service/container literally named `web`

validate_utf8 incorrectly accepts invalid 2-byte UTF-8 sequences containing ASCII characters

Admin API returns 500 instead of 400 for INVALID_FOREIGN_KEY / INVALID_WORKSPACE errors

response-transformer logs spurious "body transform failed" warnings on large/chunked JSON responses

Kong 3.7.1 Exponential memory growth over time.

kong.vault.get() dedupes pending init-phase secrets by the wrong table key

Latency (EWMA) balancer's power-of-two-choices degrades into a full scan for 3+ targets