Resource conservation for containerized systems

Patent metadata

Field	Value
Publication number	US-11907762-B2
Application number	US-202117159127-A
Country	US
Kind code	B2
Filing date	Jan 26, 2021
Priority date	Oct 30, 2018
Publication date	Feb 20, 2024
Grant date	Feb 20, 2024

Abstract

A method for conserving resources in a distributed system includes receiving an event-criteria list from a resource controller. The event-criteria list includes one or more events watched by the resource controller and the resource controller controls at least one target resource and is configured to respond to events from the event-criteria list that occur. The method also includes determining whether the resource controller is idle. When the resource controller is idle, the method includes terminating the resource controller, determining whether any event from the event-criteria list occurs after terminating the resource controller, and, when at least one event from the event-criteria list occurs after terminating the resource controller, recreating the resource controller.

First claim

What is claimed is:

1. A computer-implemented method when executed by data processing hardware causes the data processing hardware to perform operations comprising:
receiving, from a distributed computing system, a system metric for computing resources associated with a pod deployment of containerized applications hosted at the distributed computing system, each pod of the pod deployment executing one of the containerized applications, the pod deployment having a deployment size that specifies a number of pods in the pod deployment;
determining whether the system metric satisfies a threshold resource metric, the threshold resource metric indicating a target resource utilization for the pod deployment of containerized applications;
when the system metric fails to satisfy the threshold resource metric, scaling the pod deployment by decreasing the number of pods in the pod deployment based on adjusting the deployment size of the pod deployment; and
when the system metric satisfies the threshold resource metric, maintaining the deployment size for the pod deployment.

2. The method of claim 1 , wherein scaling the pod deployment by decreasing the number of pods in the pod deployment comprises downscaling the pod deployment to zero such that respective resources reserved for the pod deployment are returned to an available resource pool.

3. The method of claim 2 , wherein downscaling the pod deployment to zero comprises:
setting the deployment size of the pod deployment to zero; and
terminating the containerized applications operating in the pod deployment.

4. The method of claim 2 , wherein the operations further comprise, after downscaling the pod deployment to zero:
determining that the system metric satisfies the threshold resource metric; and
scaling the pod deployment to increase a number of containerized applications operating in the pod deployment from zero to an integer number greater than or equal to one.

5. The method of claim 4 , wherein scaling the pod deployment to increase the number of containerized applications operating in the pod deployment comprises determining that a priority designation for the pod deployment is a greatest priority designation among a plurality of pod deployments.

6. The method of claim 1 , wherein the operations further comprise receiving an event-criteria list from a deployment controller associated with the pod deployment, the event-criteria list comprising one or more events watched by the deployment controller, the deployment controller configured to respond to events from the event-criteria list that occur with respect to the pod deployment.

7. The method of claim 6 , wherein scaling the pod deployment by decreasing the number of pods in the pod deployment comprises downscaling the pod deployment to zero such that respective resources reserved for the pod deployment are returned to an available resource pool when the deployment controller corresponding to the pod deployment is idle.

8. The method of claim 6 , wherein determining whether the deployment controller is idle comprises:
analyzing events that have occurred during a threshold period of time; and
determining that the deployment controller is idle when no events on the event-criteria list have occurred within the threshold period of time.

9. The method of claim 1 ,
wherein, when a second system metric for computing resources associated with a second pod deployment satisfies the threshold resource metric, the operations further comprise:
determining that the second pod deployment is idle based on an event-criteria list for a deployment controller; and
preventing a termination procedure from terminating the idle second pod deployment.

10. The method of claim 1 , wherein a deployment controller is configured to control pod deployment of the containerized applications.

11. A system comprising:
data processing hardware; and
memory hardware in communication with the data processing hardware, the memory hardware storing instructions that when executed on the data processing hardware cause the data processing hardware to perform operations comprising:
receiving, from a distributed computing system, a system metric for computing resources associated with a pod deployment of containerized applications hosted at the distributed computing system, each pod of the pod deployment executing one of the containerized applications, the pod deployment having a deployment size that specifies a number of pods in the pod deployment;
determining whether the system metric satisfies a threshold resource metric, the threshold resource metric indicating a target resource utilization for the pod deployment of containerized applications;
when the system metric fails to satisfy the threshold resource metric, scaling the pod deployment by decreasing the number of pods in the pod deployment based on adjusting the deployment size of the pod deployment; and
when the system metric satisfies the threshold resource metric, maintaining the deployment size for the pod deployment.

12. The system of claim 11 , wherein scaling the pod deployment by decreasing the number of pods in the pod deployment comprises downscaling the pod deployment to zero such that respective resources reserved for the pod deployment are returned to an available resource pool.

13. The system of claim 12 , wherein downscaling the pod deployment to zero comprises:
setting the deployment size of the pod deployment to zero; and
terminating the containerized applications operating in the pod deployment.

14. The system of claim 12 , wherein the operations further comprise, after downscaling the pod deployment to zero:
determining that the system metric satisfies the threshold resource metric; and
scaling the pod deployment to increase a number of containerized applications operating in the pod deployment from zero to an integer number greater than or equal to one.

15. The system of claim 14 , wherein scaling the pod deployment to increase the number of containerized applications operating in the pod deployment comprises determining that a priority designation for the pod deployment is a greatest priority designation among a plurality of pod deployments.

16. The system of claim 11 , wherein the operations further comprise receiving an event-criteria list from a deployment controller associated with the pod deployment, the event-criteria list comprising one or more events watched by the deployment controller, the deployment controller configured to respond to events from the event-criteria list that occur with respect to the pod deployment.

17. The system of claim 16 , wherein scaling the pod deployment by decreasing the number of pods in the pod deployment comprises downscaling the pod deployment to zero such that respective resources reserved for the pod deployment are returned to an available resource pool when the deployment controller corresponding to the pod deployment is idle.

18. The system of claim 16 , wherein determining whether the deployment controller is idle comprises:
analyzing events that have occurred during a threshold period of time; and
determining that the deployment controller is idle when no events on the event-criteria list have occurred within the threshold period of time.

19. The system of claim 11 ,
wherein, when a second system metric for computing resources associated with a second pod deployment satisfies the threshold resource metric, the operations further comprise:
determining that the second pod deployment is idle based on an event-criteria list for

Assignees

• Google Llc

Inventors

• Barbara Justin Santa
• Hockin Timothe
• Bailey Robert
• Johnson Jeffrey

Classifications

• G06F9/5027

  the resource being a machine, e.g. CPUs, Servers, Terminals · CPC title

• G06F9/5022 Primary

  Mechanisms to release resources · CPC title

• G06F9/5016

  the resource being the memory · CPC title

• G06F9/542 Primary

  Event management; Broadcasting; Multicasting; Notifications · CPC title

• G06F9/5005

  to service a request · CPC title