Method and apparatus for virtual node to acquire monitoring metrics of internal container
Patent Information
- Application Number
- PCT/CN2024/138523
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2024-04-29
- Filing Date
- 2024-12-11
- Publication Date
- 2026-01-08
AI Technical Summary
Virtual nodes cannot monitor the cAdvisor metrics of containers inside Kata Containers, resulting in inconsistent container monitoring and an inability to upload data uniformly to the Prometheus system in the Kubernetes cluster.
By injecting the cAdvisor container into Kata Containers and intercepting Pod creation requests using the Mutating Webhook mechanism, the cAdvisor container is injected. Container metric information is then obtained and aggregated through virtual nodes to provide a unified monitoring service.
It enables virtual nodes to monitor containers inside Kata Containers, improving the uniformity and reliability of container monitoring, ensuring the accuracy and consistency of monitoring data, and supporting unified configuration to the Prometheus system.
Smart Images
Figure CN2024138523_08012026_PF_FP_ABST
Abstract
Description
Method and device for virtual node to acquire monitoring index of internal container
[0001] The present application claims priority from the Chinese patent application No. 202410525434.7, filed on April 29, 2024, and entitled "Method and device for virtual node to acquire monitoring index of internal container", the contents of which are hereby incorporated by reference in its entirety. TECHNICAL FIELD
[0002] The present application relates to the technical field of virtual nodes, and in particular to a method and device for a virtual node to acquire monitoring index of an internal container. BACKGROUND
[0003] A virtual node realizes seamless connection between Kubernetes and an elastic container instance (ECI), so that the Kubernetes cluster has greater flexibility. The ECI instance uses Kata Containers as the underlying container, which can provide hardware-level isolation inside the container and has better security and isolation. By using the ECI instance and Kata Containers in combination, the virtual node can provide a more secure, efficient and reliable container running environment for users. In terms of container monitoring, the virtual node also needs to collect data such as CPU (Central Processing Unit), memory, network and disk of the container, and needs to support uploading the collected cAdvisor monitoring index data to the Prometheus monitoring system of the Kubernetes cluster for unified container index monitoring.
[0004] An ordinary node Kubelet can easily obtain container monitoring index data through the cAdvisor interface integrated by itself, however, the virtual node itself does not provide a cAdvisor interface and cannot collect container monitoring indexes, and the underlying Kata Containers cannot collect monitoring indexes of the internal container through the external cAdvisor due to better isolation. Although Kata Containers provides a Kata Monitor tool for monitoring container indexes and performance, the indexes are inconsistent and difficult to convert into unified cAdvisor monitoring indexes, which has become a technical problem to be solved urgently. SUMMARY
[0005] In view of the above prior art deficiencies, the purpose of the application is to provide a method and device for virtual nodes to obtain monitoring indicators of internal containers, which not only solves the problem that virtual nodes cannot monitor container indicators, but also solves the problem of monitoring cAdvisor indicators of Kata Containers internal containers by virtual nodes, thereby improving the container monitoring capability and reliability of virtual nodes.
[0006] In a first aspect of the application, a method for virtual nodes to obtain monitoring indicators of internal containers is provided, comprising:
[0007] S1, creating and running a Pod supporting Kata Containers, and injecting a Pod meeting preset conditions into a cAdvisor container to collect monitoring indicators of internal containers of the Kata Containers;
[0008] S2, the virtual node obtains and summarizes container indicator information by requesting a cAdvisor port according to Pod attribute information, and provides an indicator monitoring service externally.
[0009] Further, in step S1, when injecting the cAdvisor container, the installation of an injection controller needs to be implemented, the injection controller being used for injecting the created Pod; when installing the injection controller, a Mutating Webhook Configuration resource is created for intercepting a created Pod request; when the APIServer receives the created Pod request, the injection controller intercepts, and the Pod meeting the screening conditions will be injected into the cAdvisor container configuration.
[0010] Further, injecting the cAdvisor container specifically includes the following sub-steps:
[0011] S101, when creating the Kata Containers, the Kata agent creates the cAdvisor container according to preset configuration information, and the injection controller establishes a communication connection with the APIServer based on the Kubernetes specification;
[0012] S102, the injection controller parses an incoming CA certificate file, creates a plurality of Webhooks according to the Mutating Webhook Configuration, and registers the created Webhooks on the APIServer; when a user creates a Pod, a callback Webhook is triggered, and the created Pod request is forwarded to the Webhook;
[0013] S103、The Webhook returns the created Pod to the injection controller, and the injection controller checks whether the Label of the created Pod belongs to a virtual node, and configures the Pod whose Label belongs to a virtual node to inject a cAdvisor container.
[0014] Further, in step S2, the virtual node requests the cAdvisor port in the Kata Containers to obtain container monitoring index data according to the IP information of the Pod managed by the virtual node, aggregates container index data of all Pods, supplements complete container index information, caches the latest container index data, and finally provides an index monitoring service externally by using an https service.
[0015] Further, in step S2, the virtual node obtains container index information through the cAdvisor port according to the Pod attribute information, and provides an index monitoring service externally, and specifically includes the following sub-steps:
[0016] Step S201, the virtual node initializes and creates a container index information collection service process, sets a collection service period, uses an Informer mechanism to listen to and obtain a Pod list managed by the virtual node;
[0017] Step S202, the virtual node determines a cAdvisor port according to IP information of each Pod in the Pod list, and requests the cAdvisor port to obtain container index information according to the collection service period;
[0018] Step S203, according to the information of each Pod, the container index information obtained from the cAdvisor port is filled; the filled information includes container name field information;
[0019] Step S204, the filled container index information is cached, and the cached container index information is updated regularly;
[0020] Step S205, an https external interface service is created, and when receiving a request of an upper layer to obtain container index information data from the cAdvisor port, the cached data is directly returned.
[0021] A device for a virtual node to obtain monitoring indexes of internal containers, the device comprising an injection module and an external service module;
[0022] The injection module is configured to create and run a Pod supporting Kata Containers, and inject a Pod meeting a preset condition into a cAdvisor container to collect monitoring indexes of internal containers of the Kata Containers;
[0023] The external service module is configured to acquire and aggregate container index information by requesting a cAdvisor port according to Pod attribute information, and provide an index monitoring service externally.
[0024] Further, when the cAdvisor container is injected, the injection module implements installation of an injection controller configured to inject the created Pod; when the injection controller is installed, a Mutating Webhook Configuration resource is created to intercept a Pod creation request; when the APIServer receives the Pod creation request, the injection controller intercepts the request, and a Pod meeting a screening condition is injected with the cAdvisor container configuration.
[0025] Further, in the external service module, the Pod injected with the cAdvisor container requests a cAdvisor port in the Kata Containers to acquire container monitoring index data according to IP information of the Pod managed by the Pod, aggregates container index data of all Pods, supplements complete container index information, caches the latest container index data, and finally provides an index monitoring service externally by using an https service.
[0026] In a third aspect, the application provides an electronic device, which comprises a memory and one or more processors.
[0027] The memory stores one or more application programs, and the one or more application programs are adapted to be executed by the one or more processors to implement the above method.
[0028] In a fourth aspect, the application provides a computer-readable storage medium, which stores a computer program capable of being loaded and executed by a processor to implement the above method.
[0029] The application has the following advantages:
[0030] (1) The technical solution of the application has innovation in solving the problem that a virtual node cannot monitor container indexes and Kata Containers cannot provide unified cAdvisor container monitoring indexes, and effectively improves the monitoring capability of a cluster, thereby providing more comprehensive and accurate container monitoring data support for users.
[0031] (2) The technical solution of the application has significant advantages in practicability, can effectively provide unified and convenient container monitoring index configuration, avoid data inconsistency, and provide accurate and reliable monitoring data support for users. BRIEF DESCRIPTION OF DRAWINGS
[0032] The accompanying drawings are included to provide a further understanding of embodiments of the application, and are incorporated in and constitute a part of this specification. The drawings illustrate embodiments of the application and, together with the description, serve to explain principles of the present application. In the drawings:
[0033] Fig. 1 is a schematic diagram of a technical architecture;
[0034] Fig. 2 is a schematic diagram of a process of creating a Pod injecting a cAdvisor container;
[0035] Fig. 3 is a schematic diagram of a process of generating and obtaining container monitoring metric data. DETAILED DESCRIPTION
[0036] In order to make the personnel in the art better understand the technical solutions in the embodiments of the present application, the technical solutions of the present application will be described clearly and completely below in conjunction with the drawings. Obviously, the described embodiments are only some of the embodiments of the present application, rather than all the embodiments. It should be understood that these descriptions are only exemplary, and are not used to limit the scope of the present application. Based on the embodiments of the present application, all other embodiments obtained by those of ordinary skill in the art without creative labor should fall within the scope of protection of the present application.
[0037] In addition, in the following description, the description of well-known structures and techniques has been omitted to avoid unnecessary confusion of the concepts disclosed in the present application.
[0038] In the description of the present application, it should be noted that, unless otherwise explicitly specified and limited, the orientation or positional relationship indicated by the terms "center", "upper", "lower", "left", "right", "vertical", "horizontal", "inner", "outer" and the like is based on the orientation or positional relationship shown in the drawings, and is only for the convenience of describing the present application and simplifying the description, and therefore cannot be understood as indicating or implying that the device or element referred to must have a particular orientation, be constructed and operated in a particular orientation, and therefore cannot be understood as limiting the present application. In addition, the terms "first", "second", "third" are only for the purpose of description, and cannot be understood as indicating or implying relative importance. The terms "mounting", "connecting", "connection" should be understood broadly, for example, it can be fixed connection, or detachable connection, or integral connection; it can be mechanical connection, or electrical connection; it can be direct connection, or indirect connection through an intermediate medium, or internal communication of two elements. For those of ordinary skill in the art, the specific meaning of the above terms in the present application can be understood according to the specific circumstances.
[0039] The exemplary embodiments will be described in detail herein with reference to the attached drawings. The description of the exemplary embodiments is intended to apply to any exemplary embodiment, unless specified otherwise. It is believed that the exemplary embodiments will be more fully understood from the following description taken in conjunction with the accompanying drawings, in which like reference characters refer to like elements throughout the different views. The exemplary embodiments described in the following description are not meant to be exhaustive or to be limited to the precise form disclosed. They are chosen and described herein for the purpose of explanation and understanding.
[0040] The technical architecture of the technical solution of the present application is shown in FIG. 1. The technical architecture mainly includes two parts: Kata Containers injecting a cAdvisor container and a virtual node providing a cAdvisor interface to the outside. Before describing the technical solution of the present application in detail, the related technical terms in the technical solution are described as follows:
[0041] ECI (Elastic Container Instance): a full-maintenance lightweight container instance service.
[0042] Kata Containers: referred to as Kata container, aiming to provide a secure container runtime environment, which uses lightweight virtualization technology to isolate each container into an independent virtual machine. This isolation technology can provide higher security and reliability, and can also improve the performance and efficiency of the container.
[0043] cAdvisor: used to collect, aggregate, process and export performance data and resource utilization data of containers. It can monitor the resource usage of containers such as CPU, memory, disk and network, and also provide running state information and event records of containers.
[0044] Virtual node: based on the Virtual Kubelet technology of the Kubernetes community, ECI can access the Kubernetes cluster through the virtual node, that is, the ECI instance will not run on a centralized real node, but will be scattered and distributed in the entire ECI resource pool.
[0045] In a first aspect, the present application provides a method for a virtual node to obtain cAdvisor monitoring indicators of internal containers of Kata Containers, which includes the following steps:
[0046] Step S1, creating and running a Pod supporting Kata Containers, and injecting the Pod meeting the preset conditions into a cAdvisor container to collect monitoring indicators of internal containers of Kata Containers;
[0047] In the step S1, each Kata Containers is an independent lightweight virtual machine, and the container index inside Kata cannot be collected from the outside. Therefore, when creating a Kata Containers, a cAdvisor container needs to be injected as a sidecar container at the same time, which is responsible for collecting the monitoring index of the container inside the Kata Containers.
[0048] When injecting the cAdvisor container, the installation of an injection controller needs to be implemented, which is used for injecting the created Pod; when installing the injection controller, a Mutating Webhook Configuration resource is created, which is used for intercepting the creation of a Pod request; when the APIServer receives the creation of a Pod request, the injection controller intercepts it, and the Pod meeting the screening condition will be injected with the cAdvisor container configuration.
[0049] In the step S1, injecting the cAdvisor container specifically includes the following sub-steps, as shown in FIG. 2:
[0050] In step S101, when creating a Kata Containers, a Kata agent creates a cAdvisor container according to preset configuration information, and the injection controller establishes a communication connection with the APIServer based on the Kubernetes specification;
[0051] In step S102, the injection controller parses the incoming CA certificate file, and creates a plurality of Webhooks according to the Mutating Webhook Configuration, and registers the created Webhooks on the APIServer; when a user creates a Pod, a callback Webhook is triggered, and the creation of a Pod request is forwarded to the Webhook;
[0052] In step S103, the Webhook returns the creation of a Pod request to the injection controller, the injection controller checks whether the Label of the created Pod belongs to a virtual node, and configures the Pod whose Label belongs to the virtual node to inject the cAdvisor container; the cAdvisor container provides a container index monitoring service to the outside by listening to the corresponding port.
[0053] In step S2, the virtual node obtains and summarizes the container index information by requesting the cAdvisor port according to the Pod attribute information, and provides an index monitoring service to the outside.
[0054] In the above step, when the cAdvisor container injection is completed, each Kata Containers has the ability to provide cAdvisor container monitoring indicators. The virtual node requests the cAdvisor port in the corresponding Kata Containers to obtain container monitoring indicator data according to the IP information of the Pod managed by itself, aggregates all Pod container indicator data, supplements complete container indicator information, caches the latest container indicator data, and finally provides an indicator monitoring service externally using an https service.
[0055] In the above step S2, the virtual node obtains container indicator information through the cAdvisor port according to the Pod attribute information and provides an indicator monitoring service externally, and specifically includes the following sub-steps, as shown in FIG. 3:
[0056] Step S201, the virtual node initializes and creates a container indicator information collection service process, sets a collection service period, uses an Informer mechanism to listen to and obtain a Pod list managed by itself;
[0057] In the above step, in order to avoid frequent calling of an API server to obtain a pod list and reduce system overhead, the virtual node uses an Informer mechanism to listen to and obtain a pod list managed by itself. The Informer is a component for monitoring resources in Kubernetes, which realizes the listening to resources through a ListWatch mechanism. The above collection service period is set to collect container indicator information data once every 1 minute by default;
[0058] Step S202, the virtual node determines a cAdvisor port according to the IP information of each Pod in the Pod list, and requests the cAdvisor port to obtain container indicator information according to the collection service period;
[0059] Step S203, according to the information of each Pod, the container indicator information obtained from the cAdvisor port is filled; the filled information includes container name field information;
[0060] Step S204, the filled container indicator information is cached, and the cached container indicator information is updated regularly;
[0061] Step S205, an https external interface service is created, and when receiving a request of an upper layer for container indicator information data of the cAdvisor port, the cached data is directly returned.
[0062] In the above step, the upper layer requests the cAdvisor port, for example, requests a / metrics / cAdvisor port.
[0063] Further illustrated below are specific application examples as follows:
[0064] 1) Prepare three virtual machines configured as 4-core CPUs and 8G memories, deploy a high-availability (1 Master node) Kubernetes cluster, and open the elastic container instance (ECI) service.
[0065] 2) Create a virtual node in the ECI console and bind the Kubernetes cluster, and the node of the virtual node can be seen in the Kubernetes cluster.
[0066] 3) Install the sidecar-injector component on the ECI cluster using helminstall, which is deployed in the form of a single replica Deployment and automatically registers a mutatingwebhook.
[0067] 4) Edit several Pods on the Kubernetes cluster, set the Yaml file of the Pod, add the Label of the virtual node to the Pod, create and start the Pod, and schedule the Pod to the virtual node.
[0068] 5) Observe whether the Pods are successfully running in the ECI instance, and check whether the cAdvisor container exists in the Kata Containers container group in the underlying ECI.
[0069] 6) At this time, call the / metrics / cAdvisor interface of the virtual node, and the container monitoring index data in the Kata Containers will be returned in the response data.
[0070] In a second aspect, the present application provides a device for a virtual node to obtain cAdvisor monitoring indexes of internal containers of Kata Containers, which includes two parts of an injection module and an external service module.
[0071] The injection module is used to create and run a Pod supporting Kata Containers, and inject the Pod meeting the preset condition into a cAdvisor container to collect monitoring indexes of internal containers of Kata Containers.
[0072] The external service module is used to obtain and summarize container index information by requesting a cAdvisor port according to Pod attribute information, and provide an index monitoring service externally.
[0073] In a third aspect, the present application provides an electronic device including a memory and one or more processors.
[0074] The memory stores one or more application programs adapted to be executed by the one or more processors to implement the method of acquiring cAdvisor monitoring indicators of Kata Containers internal containers of the first aspect.
[0075] The electronic device includes a processor and a memory.
[0076] The structure of the electronic device does not constitute a limitation on the embodiments of the present application.
[0077] The processor can be a CPU, a general-purpose processor, a DSP, an ASIC, an FPGA, or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute various exemplary logical blocks, modules, and circuits described in combination with the disclosure. The processor can also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.
[0078] The bus can include a path for transmitting information between the above-mentioned components. The bus can be a PCI bus or an EISA bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc.
[0079] The memory can be a ROM or other type of static storage device that can store static information and instructions, a RAM or other type of dynamic storage device that can store information and instructions, an EEPROM, a CD-ROM or other optical disk storage, an optical disk storage (including a compact disk, a laser disk, an optical disk, a digital versatile disk, a Blu-ray disk, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but not limited to this.
[0080] In a fourth aspect, the present application provides a computer-readable storage medium having a computer program stored thereon, which can be loaded and executed by a processor to implement the method of acquiring cAdvisor monitoring indicators of Kata Containers internal containers of the first aspect.
[0081] In summary, the present application aims to solve the problems of virtual nodes being unable to monitor container indicators and Kata Containers not supporting cAdvisor monitoring indicators by using the Mutating Webhook mechanism and the cAdvisor agent component self-developed virtual node to collect monitoring indicators of Kata Containers internal containers.
[0082] For the problem that virtual nodes cannot monitor container metrics: virtual nodes themselves do not provide cAdvisor interfaces and have no ability to monitor container metrics. The present application realizes the ability of virtual nodes to provide cAdvisor container monitoring metrics to the outside, and uniformly provides container monitoring metrics consistent with ordinary nodes to report to the Prometheus system, thereby improving the observability of the system.
[0083] For the problem that Kata Containers cannot provide cAdvisor container monitoring metrics: since each Kata Containers is an independent virtual machine, it cannot collect monitoring metrics of its internal containers from the outside. The present application injects a cAdvisor container when creating a Kata Containers, which runs in the form of a sidecar container, thereby collecting monitoring metrics of all containers inside the Kata Containers, to realize unified monitoring and management of the entire Kata container and Runc container, thereby improving the maintainability of the system.
[0084] For the problem of inconsistent configuration: through the technical solution of the present application, users can uniformly configure container monitoring metrics of ordinary nodes and virtual nodes in the Prometheus monitoring system of the Kubernetes cluster. Users can conveniently monitor and count container metrics without special configuration.
[0085] For the problem of inconsistent data: by uniformly configuring container monitoring metrics of ordinary nodes and virtual nodes, the problem of inconsistent container metric statistics between different nodes can be avoided. In this way, users can obtain accurate and consistent container metric data, thereby improving the credibility and comparability of monitoring data.
[0086] As can be seen, the technical solution of the present application enables users to more conveniently use the Prometheus monitoring system for unified container metric monitoring, and also enables users to more simply configure container monitoring metrics of virtual nodes and Kata Containers, so as to more conform to the purpose of their own business monitoring capabilities. In addition, the technical solution of the present application has the advantages of virtual nodes providing the same container monitoring metrics as ordinary nodes, Kata containers providing consistent cAdvisor monitoring metrics with Runc containers, and outputting unified container monitoring metrics, thereby effectively improving the monitoring capability and maintainability of the cluster.
[0087] It should be pointed out finally that the above embodiments are only used to illustrate the technical solutions of the embodiments of the present application, but not to limit them. Although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those skilled in the art that the technical solutions recorded in the foregoing embodiments can be modified, or some technical features can be replaced equivalently; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application. Any changes or replacements that can be easily thought of by those skilled in the art within the technical scope disclosed by the present application should be covered within the protection scope of the present application.
Claims
1. A method for a virtual node to obtain monitoring metrics of an internal container, the method comprising: The method comprises the following steps: S1, creating and running a Pod supporting Kata Containers, and injecting the Pod meeting preset conditions into a cAdvisor container to collect monitoring indexes of internal containers of the Kata Containers; S2, a virtual node obtaining and summarizing container index information through a cAdvisor port according to Pod attribute information, and providing an index monitoring service externally.
2. The method for a virtual node to acquire monitoring indexes of an internal container according to claim 1, wherein, In step S1, when the cAdvisor container is injected, an injection controller needs to be installed, which is used to inject the created Pod; when the injection controller is installed, a Mutating Webhook Configuration resource is created, which is used to intercept a Pod creation request; when the APIServer receives the Pod creation request, the injection controller intercepts it, and the Pod meeting the screening conditions will be injected into the cAdvisor container configuration.
3. The method of claim 1 or 2, wherein the method further comprises: The injection of the cAdvisor container specifically comprises the following sub-steps: S101, when the Kata Containers are created, a cAdvisor container is created by Kataagent according to preset configuration information, and the injection controller establishes a communication connection with the APIServer based on the Kubernetes specification; S102, the injection controller parses an incoming CA certificate file, creates a plurality of Webhooks according to the Mutating Webhook Configuration, and registers the created Webhooks on the APIServer; when a user creates a Pod, a callback Webhook is triggered, and the Pod creation request is forwarded to the Webhook; S103, the Webhook returns the created Pod to the injection controller, the injection controller checks whether the Label of the created Pod belongs to the virtual node, and configures the Pod whose Label belongs to the virtual node to inject the cAdvisor container.
4. The method of claim 1, wherein the virtual node obtains the monitoring index of the internal container. In step S2, the virtual node requests a cAdvisor port in the Kata Containers to obtain container monitoring index data according to IP information of the Pod managed by the virtual node, summarizes container index data of all the Pods, supplements complete container index information, caches the latest container index data, and finally provides an index monitoring service externally by using an https service.
5. The method of claim 1 or 4, wherein the method further comprises: In step S2, the virtual node obtains container index information through the cAdvisor port according to Pod attribute information, and provides an index monitoring service externally, which specifically comprises the following sub-steps: Step S201, the virtual node initializes and creates a container index information collection service process, sets a collection service period, and uses an Informer mechanism to listen to and obtain a Pod list managed by itself; In step S202, the virtual node determines the cAdvisor port according to the IP information of each Pod in the Pod list, and requests the cAdvisor port to obtain the container index information according to the collection service period. In step S203, the container index information obtained from the cAdvisor port is filled according to the information of each Pod. The filled information includes the container name field information. In step S204, the filled container index information is cached, and the cached container index information is updated at a fixed time. In step S205, an https external interface service is created, and when the upper layer requests the cAdvisor port to obtain the container index information data, the cached data is directly returned.
6. An apparatus for a virtual node to obtain monitoring metrics of an internal container, the apparatus comprising: The device comprises an injection module and an external service module. The injection module is configured to create and run a Pod supporting Kata Containers, and inject the Pod meeting the preset condition into a cAdvisor container to collect monitoring indexes of the internal container of the Kata Containers. The external service module is configured to request the cAdvisor port to obtain and aggregate the container index information according to the Pod attribute information, and provide an index monitoring service externally.
7. The apparatus for obtaining monitoring indicators of an internal container of a virtual node according to claim 6, wherein, When the cAdvisor container is injected, the injection module installs an injection controller, which is configured to inject the created Pod. When the injection controller is installed, a Mutating Webhook Configuration resource is created to intercept the Pod creation request. When the APIServer receives the Pod creation request, the injection controller intercepts the request, and the Pod meeting the screening condition is injected into the cAdvisor container configuration.
8. The apparatus for obtaining monitoring indicators of internal containers of a virtual node according to claim 6, wherein, In the external service module, the Pod injected with the cAdvisor container requests the cAdvisor port in the corresponding Kata Containers to obtain the container monitoring index data according to the IP information of the Pod managed by the Pod, aggregates the container index data of all Pods, supplements the complete container index information, caches the latest container index data, and finally provides an index monitoring service externally by using an https service.
9. An electronic device, comprising: The electronic device includes a memory and one or more processors; The memory stores one or more applications adapted to be executed by the one or more processors to implement the method of any one of claims 1-5.
10. A computer-readable storage medium having stored thereon a computer program, the computer program being loadable and executable by a processor to implement the method of any one of claims 1-5.