Detection and cleanup of unused microservices
Systems and methods for detection and cleanup of unused microservices. An example method comprises: identifying, by a processing device, a microservice in a running state; identifying a network proxy associated with the microservice; monitoring traffic between the network proxy and the network; determining that the network proxy has no traffic with the network during a window, wherein the window is a predetermined period of time or a predetermined amount of data that is sent to or from the network; and deleting the microservice and the network proxy.
1. A method comprising:
identifying, by a processing device, a microservice in a running state, wherein the microservice is associated with one or more replicas, each of the one or more replicas having an associated network proxy;
identifying each network proxy associated with the one or more replicas of the microservice;
monitoring traffic between each network proxy and the network;
determining that each network proxy has no traffic with the network during a window, wherein the window is a predetermined period of time or a predetermined amount of data that is sent to or from the network; and
deleting the microservice, each network proxy, and the one or more replicas associated with the microservice.
2. The method of claim 1 , wherein identifying the microservice in the running state further comprises:
determining that the microservice is on a list of running microservices.
3. The method of claim 1 , further comprising deleting an access point associated with the microservice.
4. The method of claim 1 , further comprising deleting a router service associated with the microservice.
5. The method of claim 1 , further comprising deleting a container image associated with the microservice.
6. A system comprising:
a memory;
a processing device operatively coupled to the memory, the processing device to:
identify a microservice in a running state, wherein the microservice is associated with one or more replicas, each of the one or more replicas having an associated network proxy;
identify each network proxy associated with the one or more replicas of the microservice;
monitor traffic between each network proxy and the network;
determine that each network proxy has no traffic with the network during a window, wherein the window is a predetermined period of time or a predetermined amount of data that is sent to or from the network; and
delete the microservice, each network proxy, and the one or more replicas associated with the microservice.
7. The system of claim 6 , wherein identifying the microservice in the running state further comprises:
determining that the microservice is on a list of running microservices.
8. The system of claim 6 , wherein deleting the microservice is performed upon receiving an approval via a graphical user interface (GUI).
9. A non-transitory computer-readable storage medium comprising executable instructions that, when executed by a processing device, cause the processing device to:
identify a microservice in a running state, wherein the microservice is associated with one or more replicas, each of the one or more replicas having an associated network proxy;
identify each network proxy associated with the one or more replicas of the microservice;
monitor traffic between each network proxy and the network;
determine that each network proxy has no traffic with the network during a window, wherein the window is a predetermined period of time or a predetermined amount of data that is sent to or from the network; and
delete the microservice, each network proxy, and the one or more replicas associated with the microservice.
10. The non-transitory computer-readable storage medium of claim 9 , wherein identifying the microservice in the running state further comprises:
determining that when the microservice is on a list of running microservices.
11. The non-transitory computer-readable storage medium of claim 9 , further comprising executable instructions that, when executed by the processing device, cause the processing device to:
delete an access point associated with the microservice.
12. The non-transitory computer-readable storage medium of claim 9 , further comprising executable instructions that, when executed by the processing device, cause the processing device to:
delete a router service associated with the microservice.
13. The non-transitory computer-readable storage medium of claim 9 , further comprising executable instructions that, when executed by the processing device, cause the processing device to:
delete a replica of the microservice.
14. The non-transitory computer-readable storage medium of claim 9 , further comprising executable instructions that, when executed by the processing device, cause the processing device to:
delete a container image associated with the microservice.