Fault detection and correction of API endpoints in container orchestration platforms

1. A method comprising:

invoking, responsive to detecting an unresponsive microservice managed by a container orchestration platform, a microservice Application Programming Interface (API) fault management service;

identifying, by directing a test data request to a plurality of APIs, the plurality of APIs predetermined to be critical to an operation of the unresponsive microservice, an unresponsive API, the unresponsive API causing unresponsiveness of the unresponsive microservice;

determining a remedial action to correct an unresponsive state of the unresponsive API; and

communicating the remedial action to the container orchestration platform;

wherein the invoking, identifying, determining and communicating is executed by a microservice API fault manager (MAFM).

2. The method of claim 1 , further comprising:

monitoring, by the MAFM, responsive to executing the remedial action, a validity of the state of the unresponsive API.

3. The method of claim 2 , wherein the monitoring is for a predetermined time period starting from detection of a valid state of the unresponsive API.

4. The method of claim 1 , further comprising:

storing, by the MAFM, an outcome of the remedial action.

5. The method of claim 1 , wherein the determining a remedial action employs a machine-learning algorithm that modifies a remedial action determination based on historical outcome information.

6. The method of claim 1 , wherein the remedial action includes terminating a container of a microservice associated with the unresponsive API and launching a new container of the microservice.

7. The method of claim 1 , wherein the remedial action includes rescaling a number of containers, wherein each container is associated with a microservice employing at least one API.

8. The method of claim 1 , wherein the invoking is triggered by detecting an unresponsive state of the unresponsive microservice.

9. The method of claim 1 , wherein the invoking is triggered when a latency in accessing the unresponsive microservice exceeds a predetermined time threshold.

10. The method of claim 1 , wherein the invoking is triggered when a microservice becomes unresponsive after serving a predetermined number of microservice requests.

11. The method of claim 1 , wherein at least one native API of the container orchestration platform performs the remedial action.

12. A computer system, the computer system comprising one or more processors, one or more computer-readable memories, and one or more computer-readable storage devices, and program instructions stored on at least one of the one or more computer-readable storage devices for execution by at least one of the one or more processors via at least one of the one or more computer-readable memories, the stored program instructions comprising:

program instructions to invoke using a microservice application programming interface (API) fault manager (MAFM) responsive to detecting an unresponsive microservice managed by a container orchestration platform, a microservice Application Programming Interface (API) fault management service;

program instructions to identify, using the MAFM, by directing a test data request to a plurality of APIs, the plurality of APIs predetermined to be critical to an operation of the unresponsive microservice, an unresponsive API, the unresponsive API causing unresponsiveness of the unresponsive microservice;

program instructions to determine, using the MAFM, a remedial action to correct an unresponsive state of the unresponsive API; and

program instructions to communicate, using the MAFM, the remedial action to the container orchestration platform.

13. The computer system of claim 12 , further comprising:

program instructions to monitor using the MAFM, responsive to executing the remedial action, a validity of the state of the unresponsive API.

14. The computer system of claim 13 , wherein the program instructions to monitor is for a predetermined time period starting from detection of a valid state of the unresponsive API.

15. The computer system of claim 12 , further comprising:

program instructions to store an outcome of the remedial action to the MAFM.

16. The computer system of claim 12 , wherein the MAFM employs a machine-learning algorithm that modifies a remedial action determination based on historical outcome information.

17. The computer system of claim 12 , wherein at least one native API of the container orchestration platform performs the remedial action.

18. A computer program product comprising one or more computer-readable storage devices, and program instructions stored on at least one of the one or more computer-readable storage devices, the stored program instructions comprising:

program instructions to invoke using a microservice application programming interface (API) fault manager (MAFM) responsive to detecting an unresponsive microservice managed by a container orchestration platform, a microservice Application Programming Interface (API) fault management service;

program instructions to identify, using the MAFM, by directing a test data request to a plurality of APIs, the plurality of APIs predetermined to be critical to an operation of the unresponsive microservice, an unresponsive API, the unresponsive API causing unresponsiveness of the unresponsive microservice;

program instructions to determine, using the MAFM, a remedial action to correct an unresponsive state of the unresponsive API; and

program instructions to communicate, using the MAFM, the remedial action to the container orchestration platform.

19. The computer program product of claim 18 , the stored program instructions further comprising:

program instructions to monitor using the MAFM, responsive to executing the remedial action, a validity of the state of the unresponsive API.

20. The computer program product of claim 19 , wherein the program instructions to monitor is for a predetermined time period starting from detection of a valid state of the unresponsive API.