Singleton micro-service high availability

1. A method for providing singleton micro-service high availability in a telecommunications network, comprising:

providing a front-end microservice for terminating an inbound telecom interface;

providing a plurality of back-end microservices acting as worker pods;

providing an internal controller for monitoring the health of the front-end microservice and the plurality of back-end microservices;

identifying, by the internal controller, that the front-end microservice has crashed;

initiating, by the internal controller, a label change for an existing similar pod labeled as standby to active;

matching a singleton micro-service selector label criterion;

advertising the newly re-labeled existing similar pod as part of a singleton micro-service; and

receiving, by the newly relabeled pod in the telecommunications network, traffic directed on an IP address of the singleton micro-service.

2. The method of claim 1 , wherein the inbound telecom interface is an E1 interface with a CU-UP node in a telecommunications network.

3. The method of claim 1 , wherein the inbound telecom interface is an NG interface with one or more of an AMF node and an SMF node in a telecommunications network.

4. The method of claim 1 , wherein a database handles registration of the front-end microservice and the plurality of back-end microservices.

5. The method of claim 1 , further comprising using a selector that is a free text field that accepts key-value pairs, the selector including a value that indicates that the pod is selected as active.

6. The method of claim 1 , further comprising using a selector that is a free text field that accepts key-value pairs, the selector having the value “active”.

7. A non-transitory computer-readable medium, which, when executed by at least one processor, causes the at least one processor to perform steps, the steps further comprising:

identifying, by an internal controller in a telecommunications network, the internal controller for monitoring the health of a front-end microservice and a plurality of back-end microservices, that the front-end microservice has crashed;

initiating, by the internal controller, a label change for an existing similar pod labeled as standby to active;

matching a singleton micro-service selector label criterion;

advertising the newly re-labeled existing similar pod as part of a singleton micro-service; and

receiving, by the newly relabeled pod in the telecommunications network, traffic directed on an IP address of the singleton micro-service,

wherein the front-end microservice is for terminating an inbound telecom interface; and

wherein the plurality of back-end microservices act as worker pods.

8. The non-transitory computer-readable medium of claim 7 , wherein the inbound telecom interface is an E1 interface with a CU-UP node in a telecommunications network.

9. The non-transitory computer-readable medium of claim 7 , wherein the inbound telecom interface is an NG interface with one or more of an AMF node and an SMF node in a telecommunications network.

10. The non-transitory computer-readable medium of claim 7 , wherein a database handles registration of the front-end microservice and the plurality of back-end microservices.

11. The non-transitory computer-readable medium of claim 7 , the instructions further comprising using a selector that is a free text field that accepts key-value pairs, the selector including a value that indicates that the pod is selected as active.

12. The non-transitory computer-readable medium of claim 7 , the instructions further comprising using a selector that is a free text field that accepts key-value pairs, the selector having the value “active”.

13. A system, comprising:

a front-end microservice for terminating an inbound telecom interface, in a telecommunications network;

a plurality of back-end microservices acting as worker pods, in the telecommunications network; and

an internal controller for monitoring the health of the front-end microservice and the plurality of back-end microservices, in the telecommunications network,

wherein the internal controller further comprises instructions that, when executed by a processor, causes the internal controller to:

identify that the front-end microservice has crashed;

initiate a label change for an existing similar pod labeled as standby to active;

match a singleton micro-service selector label criterion; and

advertise the newly re-labeled existing similar pod as part of a singleton micro-service,

thereby causing the newly relabeled pod in the telecommunications network to receive traffic directed on an IP address of the singleton micro-service.

14. The system of claim 13 , wherein the inbound telecom interface is an E1 interface with a CU-UP node in a telecommunications network.

15. The system of claim 13 , wherein the inbound telecom interface is an NG interface with one or more of an AMF node and an SMF node in a telecommunications network.

16. The system of claim 13 , further comprising a database for handling registration of the front-end microservice and the plurality of back-end microservices.

17. The system of claim 13 , further comprising using a selector that is a free text field that accepts key-value pairs, the selector including a value that indicates that the pod is selected as active.

18. The system of claim 13 , further comprising using a selector that is a free text field that accepts key-value pairs, the selector having the value “active”.