Implanted agent within a first service container for enabling a reverse proxy on a second container
It is presented a method performed by a first software container comprising an implanted agent, which is configured to run in said first software container. The method comprise the steps, performed by the implanted agent, of: resolving an Internet Protocol, IP, address and a port of the first software container; and registering a microservice identity, the IP address and the port of the first software container in a first distributed hash table for enabling a second implanted agent running in a second software container to configure a reverse proxy running in the second software container.
1. A method performed by a second software container comprising a second implanted agent, the method comprising:
the second implanted agent obtaining a microservice identity registered in a first table, the microservice identity having been registered by a first implanted agent of a first software container; and
the second implanted agent configuring a reverse proxy running in the second software container using the microservice identity, wherein configuring the reverse proxy using the microservice identity comprises:
the second implanted agent using the microservice identity to obtain from a second table: i) a registered protocol type associated with the microservice identity, ii) a registered frontend postfix path associated with the microservice identity, and iii) a registered target path associated with the microservice identity; and
the second agent configuring the reverse proxy to use the registered protocol type, the registered frontend postfix path, and the registered target path.
2. The method of claim 1 , wherein the step of obtaining comprises obtaining an Internet Protocol (IP) address and port number of the first software container stored in association with the microservice identity; and wherein the step of configuring the reverse proxy comprises using the IP address and port number.
3. The method of claim 1 , further comprising:
configuring the reverse proxy running in the second software container by removing an absent microservice identity from the proxy when the absent microservice identity has been removed from the first distributed hash table.
4. A data processing system comprising:
a processor; and
a memory storing instructions that, when executed by the processor, cause the data processing system to:
obtain a microservice identity registered in a first table, the microservice identity having been registered by a first implanted agent of a first software container; and
configure a reverse proxy running in a second software container using the microservice identity, wherein
the data processing system is configured to configure the reverse proxy using the microservice identity by performing a process that comprises:
using the microservice identity to obtain from a second table: i) a registered protocol type associated with the microservice identity, ii) a registered frontend postfix path associated with the microservice identity, and iii) a registered target path associated with the microservice identity; and
configuring the reverse proxy to use the registered protocol type, the registered frontend postfix path, and the registered target path.
5. The data processing system of claim 4 , wherein the data processing system is further configured to obtain an IP address and port of the first software container stored in association with the microservice identity and use the IP address and port number.
6. The data processing system of claim 4 , further comprising instructions that, when executed by the processor, cause the data processing system to:
configure the reverse proxy by removing an absent microservice identity from the proxy when the absent microservice identity has been removed from the first distributed hash table.