...
Service Manager integration with Kong
When you call the Publish Service API of Service Manager, the requests body contains the IPv4 address and port of the API Publishing Function. In the response body, these values are replaced by the IP v4 Address and port of the Kong Data Plane. This allows us to Service Manager is a Go implementation of a service that calls CAPIF Core. When publishing a service through Service Manager, we create a Kong route and Kong service. The InterfaceDescription JSON element that we return in the response body is updated to point to the Kong Data Plane. Therefore, the API interface that we return from Service Discovery has the Kong host and port, and not the original service's host and port. In this way, we use Kong as a reverse proxy. Instead of calling the Publishing service directly, our Invoker's API request is proxied through Kong. This gives us the advantages of using a proxied service, such as providing caching and load balancing.
...
The Control Panel also creates Kong services and routes. As these Kng the Control Panel's Kong resources don't have the above tags, they are not affected by this clean up.
...