...

The goal of the change is to reduce number of routes in Kong. This is achieved by making routes non-tenant-specific - thus avoiding duplication of same routes per tenant.

Since routes are now not tenant-specific, they can be created/deleted immediately when module discovery information is added/deleted - which is why the logic for managing Kong routes is now in mgr-applications microservice.

Previously routes were created/deleted in Kong on entitling/unentitling application for a specific tenant - and that is why logic for managing Kong routes was in mgr-tenant-entitlements microservice.

...

• Jira Legacy
  server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MGRAPPS-35

• Jira Legacy
  server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MGRENTITLE-81

Transition process

Prerequisites

Deploy mgr-applications version 2.0.0 or later.

Enable feature toggle in mgr-applications by setting configuration property routemanagement.enable to true, e.g. via environment variable ROUTEMANAGEMENT_ENABLE = true

Disable feature toggle in mgr-tenant entitpements -entitlements by setting configuration property application.kong.enabled to false, e.g. via environment variable APPLICATION_KONG_ENABLED = false

Steps

• Enable Disable Kong routes management in mgr-applications tenant-entitlements via env variable ROUTEMANAGEMENTAPPLICATION_KONG_ENABLE ENABLED = truefalseDisable

• Enable Kong routes management in mgr-tenant-entitlements applications via env variable APPLICATIONROUTEMANAGEMENT_KONG_ENABLED ENABLE = falsetrue

• Get all module IDs from discovery information: {{am_url}}GET <mgr-applications>/modules/discovery?limit=5000

• Delete discovery information per module DELETE {{am_url}}: DELETE <mgr-applications>/modules/<module-id>/discovery

• Re-create discovery information POST {{am_url}}: POST <mgr-applications>/modules/discovery