Kubernetes-based cloud native container variable startup resource limitation method and system

Abstract

The invention discloses a Kubernetes-based cloud native container variable startup resource limitation method, relates to the technical field of information, solves the technical problem of resource waste in the container running process, and comprises the following steps: adding a limit value parameter and a duration parameter in Pod. Spec.Containers [i]. Resources in a container group API structure; creating a container group and setting a limit value parameter and a duration parameter; binding the container group with the node; enabling the Kubelet to start to start a container on the node, and configure the number of cpu cores started by the container to be limited as a limit value parameter of a container group; and starting to start a timing executor, and after the timing of the timing executor reaches the duration parameter of the container group, carrying out resource scaling operation on the configuration value with the limit value of the container cpu in the container group as the limit in Pod. Spec.Containers[i].Resources. The invention further discloses a system for variable startup resource limitation based on the Kubernetes cloud native container.

Description

technical field [0001] The present invention relates to the field of information technology, more specifically, it relates to a method and a system thereof based on Kubernetes cloud-native container variable startup resource limitation. Background technique [0002] In Kubernetes cloud-native clusters, requests and limits in the field Pod.Spec.Containers[i].Resources of the container group (Pod) are usually used to control the resource application value and limit value respectively, but this controls the container group in The resource application value and limit value in the entire life cycle, once configured, will adopt a fixed configuration from the birth to the disappearance of the container group. [0003] In many scenarios where the business is not particularly busy, this fixed resource configuration prevents the CPU and memory resources of the node from being fully utilized. For example, when container group applications are started on some nodes with sufficient resou...

AI Technical Summary

Problems solved by technology

[0004] In this scenario, if the resource limit is configured to be low, it may cause the application to start too slowly, or even the memory exceeds the limit value during startup, resulting in failure to start

When the resource limit configuration is high, it may cause the quota limit of the namespace to be exceeded, and may also cause waste of resources during operation.

[0005] In Kubernetes cloud-native clusters, VPA (Vertical Autoscaler) is usually used to dynamically change the resource application value requests of the container group, but the resource limit value limits will not be modified, and when the resource application value is automatically modified, the container will Restart, resulting in interruption of application services

Images