Global fallback route does not work #7297
Replies: 4 comments
-
Please instead do:
You are creating a service and a route but not associating them together and Kong can't figure out what to do one a route is matched. |
Beta Was this translation helpful? Give feedback.
-
@hbagdi that's the idea -- to create a single route which is not associated to any particular service, but instead does routing to any service based on Host header. btw, in Kong 2.0 such config seems not working as well:
unless you add
|
Beta Was this translation helpful? Give feedback.
-
Service mesh was removed with The removal of transparent made the feature less useful and limited, and in many cases confusing. I think we can still make a plugin to enable it. |
Beta Was this translation helpful? Give feedback.
-
I marked this as |
Beta Was this translation helpful? Give feedback.
-
Summary
I run Kong in DB-less mode with the following config:
The idea is to catch every request and proxy it by the
Host
header. In the example above only one service is provided for brevity.This config works fine for
Kong v1.4.2
, and doesn't work forKong 2.0.1
, which returnsno Service found with those values
for each requests.The upsteam is healthy and proper configs are returned by Admin API of Kong.
I see the fallback route guide in the documentation, but it includes service route, not the global one. Is there such thing as global route in
Kong v2
?Steps To Reproduce
host: s-service
to any path;no Service found with those values
.Additional Details & Logs
2.0.1
)macOS v10.14.6
; Kong is running in Dockerv2.1.0.5, engine v19.03.5
.Beta Was this translation helpful? Give feedback.
All reactions