K8s network dial testing method, device and equipment and storage medium

Abstract

The invention relates to a k8s network dial testing method, device and equipment and a storage medium, and the method comprises the steps: building a server assembly and an intelligent agent assembly, and carrying out the deployment of the server assembly and the intelligent agent assembly; starting the server component, and maintaining the internal load balance and the external load balance of the k8s cluster through the server component; dialing and testing the service of the k8s cluster through the intelligent agent component to obtain a dialing and testing result; and visualizing the dial test result to complete the k8s cluster dial test. According to the invention, dial testing can be comprehensively carried out on the k8s cluster, an abnormal machine is rapidly positioned, and the network problem processing speed is improved.

Description

Technical Field

[0001] The present invention belongs to the field of container management, and in particular relates to a k8s network dialing method, device, equipment and storage medium. Background Art

[0002] Containers are the mainstream way to deploy microservices, and k8s is the de facto standard for container orchestration. There are working nodes in large-scale k8s clusters, and k8s uses CNI plug-ins to build a large and complex container network on these nodes. The k8s cluster uses service to load balance each service, and uses coredns for service discovery. Accessing services outside the cluster usually requires ingress-nginx to provide HTTP and HTTPS routing http services from outside the cluster to services within the cluster. Any abnormality in any link in the entire service access link may affect the stability of the service, and it is also very difficult to troubleshoot.

[0003] Currently, Mirantis / k8s-netchecker is generally used to check the k8s node network. In addition, postfinance / kubenurse can be used as an open source k8s network inspection tool to check the network delay between nodes, between nodes and svc, and before ingress, as well as coredns delay. However, only one ingress address can be configured. In a large-scale production environment, multiple LBs may forward to the backend ingress cluster. In addition, the existing solution lacks dialing tests for external dependent addresses, including domain names and ip ports, resulting in insufficient coverage of dialing tests. Summary of the invention

[0004] In view of the above deficiencies in the prior art, the purpose of the invention is to provide a k8s network dialing method, device, equipment and storage medium.

[0005] The first aspect of the present invention provides a k8s network dialing method, comprising:

[0006] S1: Establish a server component and an agent component, and deploy the server component and the agent component respectively;

[0007] S2: Start the server component and maintain the internal load balancing and external load balancing of the k8s cluster through the server component;

[0008] S3: Use the intelligent agent component to dial the service of the k8s cluster and obtain the dialing result;

[0009] S4: Visualize the dial test results to complete the k8s cluster dial test.

[0010] According to a k8s network dialing method provided by the present invention, the server component in step S1 is a netcheck-server component, and the intelligent agent component is a netcheck-agent component.

[0011] According to a k8s network dialing method provided by the present invention, in step S1, the server component is deployed to the k8s cluster through deployment, and the intelligent agent component is deployed to each node respectively through daemonset.

[0012] According to a k8s network dialing method provided by the present invention, in step S2, the server component performs internal load balancing of the k8s cluster through the svc service, and performs external load balancing of the k8s cluster through the ingress entrance.

[0013] According to a k8s network dialing method provided by the present invention, step S3 specifically includes:

[0014] The intelligent body component dials the alive interface of each pod unit;

[0015] The intelligent agent component dials the server component through the svc service;

[0016] The intelligent agent component is based on the ingress entrance and configures multiple domain names to dial the internal services of the k8s cluster;

[0017] The intelligent body component dials the virtual IP address through multiple LB addresses to the link from the ingress to the svc service;

[0018] The intelligent component dials the external dependent service through the IP port or domain name.

[0019] According to a k8s network dialing method provided by the present invention, when the intelligent agent component dials an external dependent service, all external dependent services are dialed by default;

[0020] When the intelligent agent component dials the specified external dependency service, the intelligent agent component maintains communication with the kube-apiserver component to obtain the current node label. When the current node label matches the preset specified node label, the external dependency service of the current node corresponding to the matching current node label is dialed.

[0021] According to a k8s network dialing method provided by the present invention, in step S4, the server component and the intelligent body component both provide a metrics interface, and the service monitoring system performs visual monitoring of the network configuration of the k8s cluster and the dialing results through the metrics interface.

[0022] A second aspect of the present invention provides a k8s network dialing device, comprising:

[0023] Deployment module: used to deploy server components and agent components respectively;

[0024] Load balancing module: used to start the server component, and also used to maintain the internal load balancing and external load balancing of the k8s cluster through the server component;

[0025] Dial test module: used to dial the service of the k8s cluster through the intelligent component to obtain the dial test result;

[0026] Visualization module: used to visualize the dialing test results.

[0027] A third aspect of the present invention provides a k8s network dialing device, including:

[0028] A memory and at least one processor, wherein instructions are stored in the memory;

[0029] The processor calls the instructions in the memory so that the k8s network dialing device executes the k8s network dialing method as described in any one of the above items.

[0030] A fourth aspect of the present invention provides a computer-readable storage medium, on which instructions are stored. When the instructions are executed by a processor, the k8s network dialing method as described in any one of the above items is implemented.

[0031] The beneficial effects of the present invention are as follows:

[0032] The present invention provides a k8s network dialing method, device, equipment and storage medium. By deploying an agent on each node of the k8s cluster, the agent and the server are directly dialed, and the agent dials svc, ingress, coredns and external dependent addresses and domain names to quickly locate abnormal machines and improve the speed of network problem processing. The Agent deployed by the present invention can fully detect the LB, ingress, svc connectivity and domain name resolution on the entire link exposed by the service by dialing the svc, ingress and LB of the server. Multiple ingress and LB address configurations can be configured for dialing; secondly, the mutual dialing between the Agent and the server can detect the network health between pods; in addition, the Agent can dial external IP ports and domain names to promptly discover external dependent connectivity problems. It can also limit the dialing of machines that need to access external dependencies through label restrictions, reduce dirty data, and find problems more accurately.

[0033] The present invention provides a k8s network dialing method, device, equipment and storage medium, which are rich in functions. The Agent can fully detect the LB, inress, svc connectivity and domain name resolution on the entire link exposed by the service by dialing the svc, inress and LB of the server, and can be configured to dial multiple inress and LB address configurations; and the configuration is flexible. The Agent can dial the external IP port and domain name to timely discover external dependency connectivity problems. Through label limitation, the dialing can be limited to machines that need to access external dependencies, thereby reducing dirty data and discovering problems more accurately. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] The accompanying drawings are only used to illustrate specific embodiments and are not considered to limit the present invention. In the entire drawings, the same reference symbols represent the same components. Obviously, the drawings described below are only some embodiments recorded in the embodiments of the present invention. For those of ordinary skill in the art, other drawings can also be obtained based on these drawings.

[0035] Figure 1 A schematic diagram of a k8s network dialing method flow provided by an embodiment of the present invention;

[0036] Figure 2 A schematic diagram of the structure of a k8s network dialing device provided in an embodiment of the present invention.

[0037] Reference numerals:

[0038] 100. Deployment module; 200. Load balancing module; 300. Dial-up test module; 400. Visualization module. DETAILED DESCRIPTION

[0039] In order to enable those skilled in the art to better understand the technical solutions in the embodiments of the present invention, the technical solutions of the present invention will be clearly and completely described below in conjunction with the accompanying drawings. Obviously, the described embodiments are part of the embodiments of the present invention, rather than all of the embodiments. It should be understood that these descriptions are only exemplary and are not intended to limit the scope of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in the field without making creative work should fall within the scope of protection of the present invention.

[0040] Furthermore, in the following description, descriptions of well-known structures and technologies are omitted to avoid unnecessarily obscuring the concepts disclosed in the present invention.

[0041] In the description of the present invention, it should be noted that, unless otherwise clearly specified and limited, the orientation or position relationship indicated by the terms "center", "upper", "lower", "left", "right", "vertical", "horizontal", "inside", "outside", etc. is based on the orientation or position relationship shown in the drawings, which is only for the convenience of describing the present invention and simplifying the description, and does not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as a limitation of the present invention. In addition, the terms "first", "second", and "third" are only used for descriptive purposes and cannot be understood as indicating or implying relative importance. The terms "installed", "connected", and "connected" should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection, or it can be indirectly connected through an intermediate medium, or it can be a connection between the two elements. For those of ordinary skill in the art, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.

[0042] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Instead, they are merely examples of methods and systems consistent with some aspects of the present invention as detailed in the appended claims.

[0043] In order to better understand the present invention, the terms appearing in the embodiments of the present invention are explained below.

[0044] Kubernetes (K8s for short) is a portable and scalable open source platform for managing containerized workloads and services, facilitating declarative configuration and automation.

[0045] Kube-apiserver, the core component of k8s, provides http interface calls. All k8s core operations require calling kube-apiserver. The Kubernetes API server verifies and configures the data of API objects, such as pods, services, replicationcontrollers, etc. The API server provides services for REST operations and provides a front end for the shared state of the cluster, through which all other components interact.

[0046] K8s Service (svc for short) is a core concept in the Kubernetes cluster. It is mainly responsible for providing stable service discovery and load balancing functions for applications in the cluster.

[0047] CoreDNS is a key component in the Kubernetes cluster. As the DNS service within the cluster, it is responsible for processing DNS query requests within the cluster and providing functions such as service discovery and load balancing.

[0048] Ingress is an API object that manages external access to services in a k8s cluster. The typical access method is HTTP. Ingress can provide load balancing, SSL termination, and name-based virtual hosting.

[0049] LB is the abbreviation of Load Balance, which is one of the essential architecture strategies for building large websites. Its purpose is to distribute user requests to multiple backend devices to balance the load of the server. Load balancers can be divided into two categories: hardware load balancers and software load balancers.

[0050] Linux Virtual Servers (LVS) use load balancing technology to combine multiple servers into one virtual server. It provides a low-cost solution with easy-to-expand load capacity to meet the rapidly growing network access needs.

[0051] Prometheus is an open source service monitoring system and time series database that provides a common data model and a fast data collection, storage, and query interface. Prometheus monitoring indicators are easy-to-understand numerical measurements. Time series refers to the changes in records over time.

[0052] Combine the following Figure 1 to Figure 2 Embodiments of the present invention are described.

[0053] like Figure 1 As shown, the first aspect of the present invention provides a k8s network dialing method, comprising:

[0054] S1: Establish a server component and an intelligent agent component, and deploy the server component and the intelligent agent component respectively.

[0055] Among them, the server component in step S1 is the netcheck-server component, and the intelligent agent component is the netcheck-agent component.

[0056] Among them, in step S1, the server component is deployed to the k8s cluster through deployment, and the intelligent agent component is deployed to each node respectively through daemonset.

[0057] Furthermore, the solution provided by the present invention includes two components, netcheck-server and netcheck-agent. The server is deployed using deployment, and copies can be specified. The number of copies to run can be specified as needed to improve availability and load balancing. The agent is deployed using daemonset, resulting in each node node, ensuring that there is an instance running on each node so that the network status of the node can be monitored in real time.

[0058] S2: Start the server component and maintain the internal load balancing and external load balancing of the k8s cluster through the server component.

[0059] Among them, in step S2, the server component performs internal load balancing of the k8s cluster through the svc service, and performs external load balancing of the k8s cluster through the ingress entrance.

[0060] When netcheck-server is started, it will perform load balancing within the cluster through the Kubernetes svc (service) mechanism to ensure that requests can be evenly distributed to each server pod. At the same time, through the ingress mechanism, external requests can be mapped to services within the cluster and load balanced, so that external users can also access the services provided by netcheck-server. In addition, each server pod will regularly dial (that is, actively initiate network requests) the corresponding agent to check the network connection status and the agent's running status.

[0061] S3: Dial the service of the k8s cluster through the intelligent component to obtain the dialing result.

[0062] Wherein, step S3 specifically includes:

[0063] The intelligent body component dials the alive interface of each pod unit;

[0064] The intelligent agent component dials the server component through the svc service;

[0065] The intelligent agent component is based on the ingress entrance and configures multiple domain names to dial the internal services of the k8s cluster;

[0066] The intelligent body component dials the virtual IP address through multiple LB addresses to the link from the ingress to the svc service;

[0067] The intelligent component dials the external dependent service through the IP port or domain name.

[0068] Furthermore, the dialing tests performed in step S3 are: the agent dials the / alive interface of each server pod to monitor the connectivity between pods; the agent dials the server through svc to monitor whether the coredns resolution and svc connectivity are normal; the agent can dial the service through ingress, and supports the configuration of multiple domain name resolutions, or dials through multiple LB addresses to detect the connectivity of the vip (virtual IP address) to ingress to svc link; the agent can dial external dependent services through IP ports or domain names to check external dependent domain name resolution and network connectivity.

[0069] Furthermore, when the agent is configured to access and dial services inside the Kubernetes cluster through ingress, Ingress is used in Kubernetes to expose services externally. It can route external traffic to the corresponding services inside the cluster according to the configured rules. Therefore, the agent dials services through ingress, which means that it simulates external requests, enters the cluster through ingress, and accesses specific services to check the reachability and performance of the services.

[0070] During the dial test process, the agent supports configuring multiple domain name resolutions, which means that the agent can access services within the cluster based on different domain names. By configuring multiple domain name resolutions, it can more flexibly simulate the scenario where external users access services through different domain names, thereby more comprehensively detecting the availability and performance of the service.

[0071] In addition to dialing services through ingress, the agent also supports dialing through multiple LB (load balancer) addresses. In a Kubernetes cluster, LB is usually used to distribute external traffic to services within the cluster. By configuring multiple LB addresses for dialing, you can simulate the scenario of external users accessing services through different load balancers to further detect the availability and performance of the service.

[0072] When the intelligent agent component dials and tests external dependent services, all external dependent services are dialed and tested by default;

[0073] When the intelligent agent component dials the specified external dependency service, the intelligent agent component maintains communication with the kube-apiserver component to obtain the current node label. When the current node label matches the preset specified node label, the external dependency service of the current node corresponding to the matching current node label is dialed.

[0074] Furthermore, the agent performs dial-up tests on all external dependencies by default. By specifying the k8s node label, it can be limited to which nodes to dial specific external dependencies. The agent calls the apiserver to obtain the label list of this node. For the limited external dependencies, the dial-up test is performed only when the label of this node matches; the agent maintains the kube-apiserver, obtains the label information of this node, updates it to the agent's configuration file, and requests the kube-apiserver. The delay is also exposed to the indicator. That is, when the agent wants to dial an external dependency, it will check whether the dependency is limited to dial-up tests only on nodes with certain labels. If so, the agent will only perform a dial-up test when the label of the current node matches the limited label to monitor the connectivity of the node to the kube-apiserver.

[0075] S4: Visualize the dial test results to complete the k8s cluster dial test.

[0076] Among them, in step S4, the server component and the intelligent agent component both provide metrics interfaces, and the service monitoring system visually monitors the network configuration of the k8s cluster and the dialing results through the metrics interface.

[0077] The above-mentioned metrics interface is a programming interface (API) that allows external systems (such as service monitoring systems) to collect and access data about the operating status of server components and agent components. These data usually include performance indicators (such as CPU usage, memory usage, response time, etc.) and possible other custom metrics. The metrics interface provides a standardized way to obtain these metrics data, allowing the monitoring system to collect information from different types of components in a consistent manner. The server and agent used in the present invention both provide metrics interfaces, and prometheus collects metrics to visualize the cluster network configuration.

[0078] like Figure 2 As shown, the second aspect of the present invention provides a k8s network dialing device, including:

[0079] Deployment module 100: used to deploy the server component and agent component respectively;

[0080] Load balancing module 200: used to start the server component, and also used to maintain internal load balancing and external load balancing of the k8s cluster through the server component;

[0081] The dialing test module 300 is used to dial the service of the k8s cluster through the intelligent agent component to obtain the dialing test result;

[0082] Visualization module 400: used to visualize the dialing test result.

[0083] A third aspect of the present invention provides a k8s network dialing device, including:

[0084] A memory and at least one processor, wherein instructions are stored in the memory;

[0085] The processor calls the instructions in the memory so that the k8s network dialing device executes the k8s network dialing method as described in any one of the above items.

[0086] above Figure 2 The k8s network dialing device in the embodiment of the present invention is described in detail from the perspective of modular functional entities. The k8s network dialing device in the embodiment of the present invention is described in detail from the perspective of hardware processing.

[0087] The k8s network dialing device provided by the present invention may have relatively large differences due to different configurations or performances, and may include one or more processors (central processing units, CPU) (for example, one or more processors) and memories, and one or more storage media for storing applications or data (for example, one or more massive storage devices). Among them, the memories and storage media may be short-term storage or persistent storage. The program stored in the storage medium may include one or more modules, each of which may include a series of instruction operations in the k8s network dialing device. Furthermore, the processor may be configured to communicate with the storage medium and execute a series of instruction operations in the storage medium on the k8s network dialing device.

[0088] The k8s network dialing device of the present invention may also include one or more power supplies, one or more wired or wireless network interfaces, one or more input and output interfaces, and / or one or more operating systems, such as WindowsServe, MacOSX, Unix, Linux, FreeBSD, etc. Those skilled in the art will appreciate that the k8s network dialing device structure provided by the present invention does not constitute a limitation on the k8s network dialing device, and may include more or fewer components than described, or combine certain components, or arrange components differently.

[0089] A fourth aspect of the present invention provides a computer-readable storage medium, on which instructions are stored. When the instructions are executed by a processor, the k8s network dialing method as described in any one of the above items is implemented.

[0090] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0091] If the integrated unit is implemented in the form of a software functional unit and sold or passed as an independent product, it can be stored in a computer-readable storage medium. Based on the understanding, the technical solution of the present invention is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk and other media that can store program codes.

[0092] The present invention provides a k8s network dialing method, device, equipment and storage medium. First, through the intelligent body component (netcheck-agent), each pod unit, server component (netcheck-server), internal service, and external dependent service in the k8s cluster are fully dialed to ensure the extensiveness of network monitoring; the dialing test is not limited to internal services, but also includes the test of external access links through ingress and multiple LB addresses, as well as the test for external dependent services, thereby providing all-round network monitoring from the inside to the outside. Second, the intelligent body component can perform conditional dialing based on node labels, that is, only dialing for external dependent services on nodes with specific labels. This flexibility makes the dialing test more efficient and targeted. The dialing test can be a default test for all external dependent services, or a customized test for specific services, meeting the monitoring needs in different scenarios. Third, the server component is deployed through the deployment method, and the intelligent component is deployed to each node through the daemonset method, ensuring the high availability and scalability of the dialing service. The server component uses the svc service to achieve internal load balancing, and achieves external load balancing through the ingress entrance, which improves the resource utilization and service response speed of the cluster. Fourth, the metrics interface provided by the server and intelligent components enables the service monitoring system to obtain the dialing results and cluster network configuration information in real time, and then display this information through visualization means. Visual monitoring not only improves the system administrator's perception of the cluster network status, but also makes problem discovery and resolution faster and more intuitive. Fifth, the combination of comprehensive network dialing and visual monitoring helps to timely discover and locate network failures, thereby reducing the service interruption time caused by network problems. The flexible dialing strategy and efficient deployment method enable the present invention to adapt to k8s clusters of different scales and complexities, improving the overall stability and reliability of the system.

[0093] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the embodiments of the present invention, rather than to limit them. Although the present invention has been described in detail with reference to the above embodiments, those skilled in the art should understand that they can still modify the technical solutions recorded in the above embodiments, or replace some of the technical features therein by equivalents; 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 invention. Any changes or replacements that can be easily thought of by those skilled in the art within the technical scope disclosed in the present invention should be covered within the protection scope of the present invention.

Claims

1. A k8s network dialing method, characterized in that: include: S1: Establish a server component and an agent component, and deploy the server component and the agent component respectively; S2: Start the server component and maintain the internal load balancing and external load balancing of the k8s cluster through the server component; S3: Use the intelligent agent component to dial the service of the k8s cluster and obtain the dialing result; S4: Visualize the dial test results to complete the k8s cluster dial test.

2. A k8s network dialing method according to claim 1, characterized in that, The server component in step S1 is a netcheck-server component, and the agent component is a netcheck-agent component.

3. A k8s network dialing method according to claim 1, characterized in that, In step S1, the server component is deployed to the k8s cluster through deployment, and the intelligent agent component is deployed to each node through daemonset.

4. A k8s network dialing method according to claim 1, characterized in that, In step S2, the server component performs internal load balancing of the k8s cluster through the svc service and performs external load balancing of the k8s cluster through the ingress entrance.

5. A k8s network dialing method according to claim 1, characterized in that: Step S3 specifically includes: The intelligent body component dials the alive interface of each pod unit; The intelligent agent component dials the server component through the svc service; The intelligent agent component is based on the ingress entrance and configures multiple domain names to dial the internal services of the k8s cluster; The intelligent body component dials the virtual IP address through multiple LB addresses to the link from the ingress to the svc service; The intelligent component dials the external dependent service through the IP port or domain name.

6. A k8s network dialing method according to claim 5, characterized in that: When the agent component dials external dependent services, all external dependent services are dialed by default; When the intelligent agent component dials the specified external dependency service, the intelligent agent component maintains communication with the kube-apiserver component to obtain the current node label. When the current node label matches the preset specified node label, the external dependency service of the current node corresponding to the matching current node label is dialed.

7. A k8s network dialing method according to claim 1, characterized in that: In step S4, the server component and the intelligent agent component both provide metrics interfaces, and the service monitoring system visually monitors the network configuration of the k8s cluster and the dialing results through the metrics interfaces.

8. A k8s network dialing device, characterized in that: include: Deployment module: used to deploy server components and agent components respectively; Load balancing module: used to start the server component, and also used to maintain the internal load balancing and external load balancing of the k8s cluster through the server component; Dial test module: used to dial the service of the k8s cluster through the intelligent component to obtain the dial test result; Visualization module: used to visualize the dialing test results.

9. A k8s network dialing device, characterized in that: include: A memory and at least one processor, wherein instructions are stored in the memory; The processor calls the instruction in the memory so that the k8s network dialing device executes the k8s network dialing method as described in any one of claims 1-7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores instructions, and when the instructions are executed by the processor, the k8s network dialing method as described in any one of claims 1-7 is implemented.

Images