Overview

There has been a change in the way how Eureka manages routes in Kong.

...

• Disable Kong routes management in mgr-tenant-entitlements via env variable APPLICATION_KONG_ENABLED = false

• Enable Kong routes management in mgr-applications via env variable ROUTEMANAGEMENT_ENABLE = true

• Get all module IDs from discovery information: execute HTTP GET on <mgr-applications>/modules/discovery?limit=5000500, pick id field from discovery array entries, mind the possible pagination - get next pages if there are any.

• Delete discovery information per module: execute HTTP DELETE on <mgr-applications>/modules/<module-id>/discovery where module-id is a module id from previous step. Execute such HTTP request for all modules. Optionally: verify that Kong routes were deleted for these modules via Kong management UI.

• Re-create discovery information: execute HTTP POST on <mgr-applications>/modules/discovery with a modules discovery information (can be the same as in GET step).

Verification

In Kong management UI, go to Gateway Services section, find some modules for which discovery information was just re-created, and check their routes - the expression section for route should NOT contain x_okapi_tenant header part. E.g. go to module details, open routes tab, open any route and check the expression field:

...