Skip to end of banner
Go to start of banner

Kong routes management migration

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Overview

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

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

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 in Kong on entitling application for a specific tenant - and that is why logic for managing Kong routes was in mgr-tenant-entitlements microservice.

Relevant Jira issues:

Transition process

Prerequisites

Deploy mgr-applications version 2.0.0 or later.

Enable feature toggle in mgr-applications via ROUTEMANAGEMENT_ENABLE = true

Disable feature toggle in mgr-tenant entitpements APPLICATION_KONG_ENABLED = false

Steps

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

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

  • Get all module IDs from discovery information: {{am_url}}/modules/discovery?limit=5000

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

  • Re-create discovery information POST {{am_url}}/modules/discovery

  • No labels