Selecting low priority pods for guaranteed runs

A computer system for service assurance, the computer system comprising:

• a bus system;
• a storage device connected to the bus system, wherein the storage device stores program instructions;
• and
• a processor connected to the bus system, wherein the processor executes the program instructions to:
• identify a low priority pod corresponding to a low priority service in an orchestration platform that is to be evicted due to a predicted peak load period of a high priority service based on analysis of historical and resource information;
• inform a user regarding disruption of the low priority service based on the eviction of the low priority pod in response to determining that the low priority service will be affected by evicting the low priority pod;
• mark the low priority service corresponding to the low priority pod that is to be evicted due to the predicted peak load period of the high priority service as an assured service for a guaranteed run in response to receiving an input from a user who was notified regarding eviction of the low priority pod;
• determine whether the user marked the low priority service as an assured service;
• provision the low priority pod corresponding to the low priority service that is to be evicted due to the predicted peak load period of the high priority service on a second host node prior to the eviction of the low priority pod from a first host node;
• and
• evict using a scheduler, the low priority pod from the first host node of the orchestration platform in response to determining that the user did not mark the low priority service as an assured service.

A computer program product for service assurance, the computer program product comprising a computer-readable storage medium having program instructions embodied therewith, the program instructions executable by a computer to cause the computer to perform a method of:

• identifying, by the computer, a low priority pod corresponding to a low priority service in an orchestration platform that is to be evicted due to a predicted peak load period of a high priority service based on analysis of historical and resource information;
• informing, by the computer, a user regarding disruption of the low priority service based on the eviction of the low priority pod in response to determining that the low priority service will be affected by evicting the low priority pod;
• marking, by the computer, the low priority service corresponding to the low priority pod that is to be evicted due to the predicted peak load period of the high priority service as an assured service for a guaranteed run in response to receiving an input from a user who was notified regarding eviction of the low priority pod;
• determining, by the computer, whether the user marked the low priority service as an assured service;
• provisioning, by the computer, the low priority pod corresponding to the low priority service that is to be evicted due to the predicted peak load period of the high priority service on a second host node prior to the eviction of the low priority pod from a first host node;
• and
• evicting, by the computer, using a scheduler, the low priority pod from the first host node of the orchestration platform in response to determining that the user did not mark the low priority service as an assured service.