CN113691647A - Domain name resolution method and device, electronic equipment and storage medium - Google Patents

Domain name resolution method and device, electronic equipment and storage medium Download PDF

Info

Publication number
CN113691647A
CN113691647A CN202110976814.9A CN202110976814A CN113691647A CN 113691647 A CN113691647 A CN 113691647A CN 202110976814 A CN202110976814 A CN 202110976814A CN 113691647 A CN113691647 A CN 113691647A
Authority
CN
China
Prior art keywords
kubernets
pod
cluster
address
service
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN202110976814.9A
Other languages
Chinese (zh)
Other versions
CN113691647B (en
Inventor
胡宝涛
周子江
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Jingdong Technology Information Technology Co Ltd
Original Assignee
Jingdong Technology Information Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Jingdong Technology Information Technology Co Ltd filed Critical Jingdong Technology Information Technology Co Ltd
Priority to CN202110976814.9A priority Critical patent/CN113691647B/en
Publication of CN113691647A publication Critical patent/CN113691647A/en
Application granted granted Critical
Publication of CN113691647B publication Critical patent/CN113691647B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/141—Setup of application sessions

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The invention provides a domain name resolution method, a domain name resolution device, electronic equipment and a storage medium, wherein an IP address corresponding to a target Pod is obtained based on receiving a dns resolution request of kubernetesservice sent by the target Pod; if the IP address is not the IP address corresponding to any Pod container in the kubernetes cluster, resolving the service domain name in the kubernetes cluster into an externalIP based on the hybrid plug-in, and sending the externalIP to the target Pod container to enable the target Pod container to establish connection with the kuberneteservice based on the externalIP. Based on the invention, the use of hardware resources can be reduced, the cost can be reduced, and the operation and maintenance efficiency can be improved.

Description

Domain name resolution method and device, electronic equipment and storage medium
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a domain name resolution method and apparatus, an electronic device, and a storage medium.
Background
With the deep development of cloud originality, the application of kubernets is more and more extensive, and in order to maintain the reliability of services, a user deploys the kubernets into different machine rooms, so that the requirement of analyzing services across kubernets clusters exists. The service address of kubernets has 2 types of IP addresses: cluster IP and external IP. Generally, deployment in coredns deployed inside kubernets can resolve the service domain name into cluster IP, but the cluster IP is a virtual IP which can only be accessed inside the kubernets cluster and cannot be accessed from outside the cluster.
Therefore, how to provide a domain name resolution method is to resolve the domain name of the service in the kubernets-1 cluster into an external IP, so as to achieve that the Pod on the VM and the kubernets-2 cluster establishes connection with the service in the kubernets-1 cluster according to the external IP obtained through resolution, which is a problem to be solved at present. Where the externalIP is a virtual IP that can be accessed from outside the kubernets cluster.
Disclosure of Invention
In view of the above, the present invention provides a domain name resolution method, device, electronic device and storage medium, so as to achieve the purpose of reducing the use of hardware resources and reducing the cost.
The invention discloses a domain name resolution method, which is applied to coredns deployed in a kubernets cluster, wherein hybrid plug-ins are deployed in the coredns, and the coredns is connected with kubernets APIServer in the kubernets cluster, and the method comprises the following steps:
receiving a dns analysis request of kubernets service sent by a target Pod;
acquiring an IP address corresponding to the target Pod based on the dns resolution request of the kubernets service;
judging whether the IP address is the IP address corresponding to any Pod container in the kubernetes cluster or not;
if the IP address is not the IP address corresponding to any Pod container in the kubernets cluster, determining that the target Pod container is not the Pod container in the kubernets cluster, and resolving the domain name of the kubernets service in the kubernets cluster into an external IP based on the hybrid plug-in;
and sending the external IP to the target Pod so that the target Pod establishes connection with the kubernets service based on the external IP.
Optionally, the method further includes:
if the IP address is the IP address corresponding to any Pod container in the kubernets cluster, determining that the target Pod container is the Pod container in the kubernets cluster, and resolving the kubernets service domain name in the kubernets cluster into a cluster IP based on the hybrid plug-in;
and sending the cluster IP to the target Pod so that the target Pod establishes connection with the kubernets service based on the cluster IP.
Optionally, before receiving a dns resolution request of a kubernets service sent by a target Pod, the method further includes:
the coredns monitors and caches domain name information of the kubernets service, wherein the domain name information of the kubernets service comprises a cluster IP and an external IP;
when the network of the kubernets cluster is configured as an overlay network, reading a target configuration file under a preset namespace, and acquiring network segment information of the overlay network from the target configuration file;
when the network of the kubernets cluster is configured as an underlay network, monitoring and acquiring container information of the kubernets cluster, wherein the container information comprises an IP address of each Pod;
based on the domain name information of the kubernets service and the network segment information/the kubernets cluster container information of the overlay network, starting dns monitoring service of the coedns, so that when the coedns monitors a dns resolution request of the kubernets service sent by the target Pod, the dns resolution request of the kubernets service sent by the target Pod is received.
Optionally, if the network of the kubernets cluster is configured as the overlay network, the determining whether the IP address is an IP address corresponding to any Pod container in the kubernets cluster includes:
if the network of the kubernets cluster is configured as the overlay network, judging whether the IP address belongs to a network segment in network segment information of the overlay network;
if the IP address does not belong to the network segment in the network segment information of the overlay network, determining that the IP address is not the IP address corresponding to any Pod in the kubernets cluster;
if the IP address belongs to the network segment in the network segment information of the overlay network, determining that the IP address is the IP address corresponding to the Pod container in the kubernets cluster.
Optionally, if the network of the kubernets cluster is configured as the underlay network, the determining whether the IP address is an IP address corresponding to any Pod container in the kubernets cluster includes:
if the network of the kubernets cluster is configured as the underlay network, judging whether the IP address is the IP address in the container information;
if the IP address is not the IP address in the container information, determining that the IP address is not the IP address corresponding to any Pod container in the kubernets cluster;
and if the IP address is the IP address in the container information, determining that the IP address is the IP address corresponding to any Pod container in the kubernets cluster.
The second aspect of the present invention discloses a domain name resolution apparatus, which is applied to a coredns deployed in a kubernets cluster, wherein a hybrid plug-in is deployed in the coredns, and the coredns is connected with a kubernets api server in the kubernets cluster, and the apparatus includes:
the receiving unit is used for receiving a dns resolution request of the kubernets service sent by the target Pod;
a first obtaining unit, configured to obtain, based on the dns resolution request of the kubernets service, an IP address corresponding to the target Pod;
a first judging unit, configured to judge whether the IP address is an IP address corresponding to any Pod in the kubernetes cluster;
a first parsing unit, configured to determine that the target Pod is not a Pod in the kubernets cluster if the IP address is not an IP address corresponding to any Pod in the kubernets cluster. Analyzing the domain name of the kubernets service in the kubernets cluster into an external IP based on the hybrid plug-in;
a first sending unit, configured to send the external IP to the target Pod, so that the target Pod establishes a connection with the kubernets service based on the external IP.
Optionally, the apparatus includes:
a second parsing unit, configured to determine that the target Pod is the Pod in the kubernets cluster if the IP address is an IP address corresponding to any one of the Pod containers in the kubernets cluster, and parse a domain name of the kubernets service in the kubernets cluster into a cluster IP based on the hybrid plug-in;
and the second sending unit is used for sending the cluster IP to the target Pod so that the target Pod establishes connection with the kubernets service based on the cluster IP.
Optionally, before executing the receiving unit, the apparatus further includes:
a monitoring unit, configured to monitor and cache domain name information of the kubernets service in the coredns, where the domain name information of the kubernets service includes clusterIP and externalIP;
the reading unit is used for reading a target configuration file under a preset name space when the network of the kubernets cluster is configured as an overlay network, and acquiring network segment information of the overlay network from the target configuration file;
a second obtaining unit, configured to monitor and obtain container information of the kubernets cluster when a network of the kubernets cluster is configured as an underlay network, where the container information includes an IP address of each Pod;
a starting unit, configured to start a dns monitoring service of the coredns based on domain name information of the kubernets service and network segment information of an overlay network/the kubernets cluster container information, so that when a dns resolution request of the kubernets service sent by the target Pod is monitored by the coredns, the dns resolution request of the kubernets service sent by the target Pod is received.
In a third aspect, the present invention discloses an electronic device, which includes a processor and a memory, where the memory is used to store program codes and data for domain name resolution, and the processor is used to call program instructions in the memory to execute the domain name resolution method disclosed in the first aspect of the present invention.
A fourth aspect of the present invention discloses a storage medium, where the storage medium includes a storage program, and when the storage program runs, the storage medium controls a device in which the storage medium is located to execute the domain name resolution method disclosed in the first aspect of the present invention.
The invention provides a domain name resolution method, a domain name resolution device, electronic equipment and a storage medium, which are applied to coredns deployed in a kubernets cluster, wherein a hybrid plug-in is deployed in the coredns deployed in the kubernets cluster, and connection between the coredns and kubernets APIServer in the kubernets cluster is established, so that after receiving a dns resolution request of kubernets service sent by a target Pod, the coredns obtains an IP address corresponding to the target Pod based on the dns resolution request of the kubernets service; judging whether the IP address is the IP address corresponding to any Pod in the kubernetes cluster or not; determining that the target Pod is not any Pod in the kubernets cluster under the condition that the IP address is not the IP address corresponding to any Pod in the kubernets cluster, and resolving the domain name of kubernets service in the kubernets cluster into an external IP based on the hybrid plug-in; and sending the external IP to the target Pod so that the target Pod establishes connection with the kubernets service based on the external IP. According to the technical scheme provided by the invention, the hybrid plug-in is deployed in the coredns deployed in the kubernets cluster, so that the domain name of the kubernets service in the kubernets cluster is resolved into the external IP directly on the basis of the hybrid plug-in under the condition that the target Pod is determined not to be any Pod container in the kubernets cluster, and a set of external coredns does not need to be deployed in the kubernets cluster, so that the use of hardware resources is reduced, and the cost is reduced.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a schematic structural diagram of a domain name resolution method in the prior art;
fig. 2 is a schematic structural diagram of a kubernets cluster according to an embodiment of the present invention;
fig. 3 is a schematic flowchart of a domain name resolution method according to an embodiment of the present invention;
fig. 4 is a schematic flowchart of another domain name resolution method according to an embodiment of the present invention;
fig. 5 is an exemplary diagram of a domain name resolution method according to an embodiment of the present invention;
fig. 6 is a schematic structural diagram of a domain name resolution apparatus according to an embodiment of the present invention;
fig. 7 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The term "include" and variations thereof as used herein are open-ended, i.e., "including but not limited to". The term "based on" is "based, at least in part, on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Relevant definitions for other terms will be given in the following description.
It should be noted that the terms "first", "second", and the like in the present disclosure are only used for distinguishing different devices, modules, or units, and are not used for limiting the order or interdependence of the functions performed by the devices, modules, or units.
It is noted that references to "a", "an", and "the" modifications in the disclosure are exemplary rather than limiting, and that those skilled in the art will understand that "one or more" unless the context clearly dictates otherwise.
In the prior art, a set of external coredns can be deployed in a kubernets-1 cluster, and a coredns external plug-in is deployed in the external coredns, as shown in fig. 1. The domain name of the service in the Kubernets-1 cluster can be resolved into an external IP through a coredns external plug-in, so that the Pod on the VM and the kubernets-2 cluster is realized, and after the domain name resolution of the service in the kubernets-1 cluster is completed, the connection between the external IP obtained through resolution and the service in the kubernets-1 cluster can be established according to the external IP obtained through resolution. However, this approach requires multiple deployments of an external coredns, which requires not only a large amount of hardware resources, but also a high cost.
Therefore, the domain name resolution method, the domain name resolution device, the electronic equipment and the storage medium provided by the invention have the advantages that the hybrid plug-in is deployed in the coredns deployed in the kubernets cluster, and the domain name of the kubernets service in the kubernets cluster is resolved into the external IP directly on the basis of the hybrid plug-in under the condition that the target Pod is determined not to be any Pod container in the kubernets cluster, so that a set of external coredns does not need to be deployed in the kubernets cluster, and further the use of hardware resources is reduced and the cost is reduced.
Referring to fig. 2, a schematic structural diagram of a kubernets cluster provided by an embodiment of the present invention is shown, where the kubernets cluster includes coredns and kubernets APIServer deployed inside, and at least one Pod container, where hybrid plug-ins are deployed in the coredns deployed inside the kubernets cluster, and the coredns deployed inside the kubernets cluster and the kubernets APIServer within the kubernets cluster have established connection.
Referring to fig. 3, a schematic flow chart of a domain name resolution method provided in the embodiment of the present invention is shown, where the domain name resolution method is applied to coredns deployed in a kubernets cluster shown in fig. 3, and the domain name resolution method specifically includes the following steps:
s301: and receiving a dns resolution request of the kubernets service sent by the target Pod.
In the specific process of step S401, after the coredns starts its own dns listening service, it may receive a dns resolution request of the kubernets service sent by a Pod container (for convenience of distinguishing, a Pod container sending a dns resolution request of the kubernets service is referred to as a target Pod container).
It should be noted that the dns resolution request of the kubernets service carries a connection manner between coredns and the target Pod, where the coredns and the target Pod may be connected by tcp or udp.
S302: and acquiring the IP address corresponding to the target Pod based on the dns resolution request of the kubernets service.
In the process of specifically executing step S302, after receiving a dns resolution request of a kubernets service initiated by the target Pod, the coredns may obtain an IP address corresponding to the target Pod according to a connection manner between the coredns carried in the dns resolution request of the kubernets service and the target Pod.
For example, if the connection mode between the coredns carried in the dns resolution request of the kubernets service and the target Pod is tcp connection, the coredns may find the target Pod through the tcp connection, and further obtain the IP address corresponding to the target Pod.
S303: judging whether the IP address is the IP address corresponding to any Pod in the kubernets cluster or not; if the IP address is not the IP address corresponding to any Pod in the kubernets cluster, go to step S304; if the IP address is the IP address corresponding to any Pod in the kubernets cluster, step S306 is executed.
In the process of specifically executing step S303, after the coredns acquires the IP address corresponding to the target Pod, it may be determined whether the target Pod is any Pod in the kubernets cluster by according to the acquired IP address corresponding to the target Pod; determining that the target Pod is a Pod in the kubernets cluster under the condition that the IP address corresponding to the target Pod is the IP address corresponding to any Pod in the kubernets cluster; and under the condition that the IP address corresponding to the target Pod is not the IP address corresponding to any Pod in the kubernets cluster, determining that the target Pod is not a Pod in the kubernets cluster.
S304: determining that the target Pod is not a Pod within the kubernets cluster, and resolving a domain name of the kubernets service within the kubernets cluster to an external IP based on the hybrid plugin.
In the specific execution process of step S304, in the case that it is determined that the target Pod is not a Pod within the kubernets cluster, the coredns resolves the domain name of the kubernets service within the kubernets cluster into an external IP through a hybrid plugin which is deployed in the inside in advance.
S305: and sending the external IP to the target Pod so that the target Pod establishes connection with the kubernets service based on the external IP.
In the specific process of executing step S305, after the cordreds resolves the domain name of the kudrenets service in the kudrenets cluster into an external IP through the hybrid plug-in deployed in the inside in advance, the resolved external IP is sent to the target Pod according to the IP address of the target Pod, and since the external IP can implement external access to the kudrenets cluster, the target Pod can establish connection with the kudrenets service according to the external IP after receiving the external IP returned by the cordreds, and then can access the kudrenets service.
S306: and determining that the target Pod is any Pod in the kubernets cluster, and resolving the kubernets service domain name in the kubernets cluster into a cluster IP based on the hybrid plug-in.
In the specific process of executing step S306, when it is determined that the target Pod is a Pod in the kubernets cluster, the coredns resolves the domain name of the kubernets service in the kubernets cluster into a cluster IP through a hybrid plugin which is deployed in the inside in advance.
S307: and sending the cluster IP to the target Pod so that the target Pod establishes connection with the kubernets service based on the cluster IP.
In the specific process of executing step S307, after the domain name of the kubernets service in the kubernets cluster is resolved into a cluster IP by the coredns through the hybrid plugin which is internally deployed in advance, the resolved cluster IP is sent to the target Pod according to the IP address of the target Pod, and since the cluster IP can realize access in the kubernets cluster, the target Pod can establish connection with the kubernets service according to the cluster IP after receiving the cluster IP returned by the coredns, and can access the kubernets service.
The invention provides a domain name resolution method, which is applied to coredns deployed in a kubernets cluster, wherein a hybrid plug-in is deployed in the coredns deployed in the kubernets cluster, and connection between the coredns and kubernets APIServers in the kubernets cluster is established, so that after receiving a dns resolution request of kubernets service sent by a target Pod, the coredns obtains an IP address corresponding to the target Pod based on the dns resolution request of the kubernets service; judging whether the IP address is the IP address corresponding to any Pod in the kubernetes cluster or not; under the condition that the IP address is not the IP address corresponding to any Pod in the kubernets cluster, determining that the target Pod is not any Pod in the kubernets cluster, and analyzing the domain name of the kubernets service in the kubernets cluster into an external IP based on the hybrid plug-in; and sending the external IP to the target Pod so that the target Pod establishes connection with the kubernets service based on the external IP. According to the technical scheme provided by the invention, the hybrid plugin is deployed in the coredns deployed in the kubernets cluster, if the IP address is the IP address corresponding to a certain Pod container in the kubernets cluster, the service domain name in the kubernets cluster is analyzed into a cluster IP based on the hybrid plugin, the target Pod container establishes connection with the kubernets service based on the cluster IP, and further, under the condition that the target Pod container is determined not to be any Pod container in the kubernets cluster, the domain name of the kubernets service in the kubernets cluster is analyzed into an external IP based on the hybrid plugin directly, the target Pod container establishes connection with the kubernets service based on the external IP, and a plurality of external coredns do not need to be deployed in the kubernets cluster, so that the use of hardware resources is reduced, and the cost of the hardware is reduced.
Referring to fig. 4, a schematic flow chart of another domain name resolution method provided in the embodiment of the present invention is shown, where the domain name resolution method is applied to coredns deployed in a kubernets cluster shown in fig. 3, and the domain name resolution method specifically includes the following steps:
s401: monitoring and caching domain name information of the kubernets services, wherein the domain name information of the kubernets services comprises a cluster IP and an external IP.
In the embodiment of the application, the coredns is deployed in the kubernets cluster, so that the domain name information of the kubernets service in the kubernets cluster can be monitored through the coredns deployed in the kubernets cluster, and when the domain name information of the kubernets service in the kubernets cluster is monitored, the monitored domain name information of the kubernets service in the kubernets cluster is obtained and cached. The domain name information of the kubernets services in the kubernets cluster is service information, and the service information comprises cluster IP and external IP.
S402: judging whether the network configuration of the kubernets cluster is an overlay network or an underlay network; if the network of the kubernets cluster is configured as an overlay network, executing step S403; if the network of the kubernets cluster is configured as an underlay network, step S404 is executed.
In the specific process of executing step S402, coerdns may determine whether the network configuration of the current kubernets cluster is an overlay network or an underlay network, and execute step S403 when determining that the network configuration of the kubernets cluster is an overlay network; in a case where it is determined that the network of the kubernets cluster is configured as an underlay network, step S404 is performed.
It should be noted that the IP address of the Pod of the kubernets cluster is determined. For overlay networks, when a Pod is typically deployed in a kubernets cluster, the IP address of the Pod is determined, e.g., 10.244. x.x; for an underlay network, an IP address, such as 10 segments, 172 segments, 192.168 segments, etc., is divided in advance from the data center for allocating Pod containers deployed in the kubernets cluster.
It should be noted that, for an overlay network, network segment information corresponding to the overlay network, for example, 10.244.0.0/16, is preset, and the set network segment information is stored in a target configuration file in a preset namespace preset in a kubernets cluster.
S403: and reading a flannel configuration file under the kube-system namespace, and acquiring network segment information of the overlay network from the configuration file.
In the specific execution process of step S403, in the case that it is determined that the network of the kubernets cluster is configured as an overlay network, reading a target configuration file in a preset namespace, and acquiring network segment information of the overlay network from the target configuration file.
It should be noted that the preset namespace may be a kube-system namespace, and the target configuration file may be a flannel configuration file, that is, when it is determined that the network configuration of the kube cluster is an overlay network, the flannel configuration file in the kube-system namespace is read, and network segment information of the overlay network is obtained from the flannel configuration file.
S404: and monitoring and acquiring container information of the kubernets cluster, wherein the container information comprises the IP address of each Pod.
In the specific execution process of step S404, in the case that it is determined that the network of the kubernets cluster is configured as an underlay network, container information of the kubernets cluster is monitored, and after the container information of the kubernets cluster is monitored, the container information of the kubernets cluster is acquired. Wherein the container information of the kubernets cluster comprises an IP address of each Pod container in the kubernets cluster.
It should be noted that the acquired container information of the kubernets cluster is also stored.
S405: based on domain name information of kubernets service and network segment information of overlay network/container information of kubernets cluster, dns monitoring service of coredns is started.
In the process of specifically executing step S405, if the network of the kubernets cluster is configured as an overlay network, the coredns starts its own dns monitoring service after acquiring domain name information of the kubernets service and network segment information of the overlay network, based on the acquired domain name information of the kubernets service and network segment information of the overlay network, so that when the coredns monitors a dns resolution request of the kubernets service sent by a target Pod, the dns resolution request of the kubernets service sent by the target Pod is received.
If the network of the kubernets cluster is configured as an underlay network, after domain name information of the kubernets service and container information of the kubernets cluster are obtained, based on the obtained domain name information of the kubernets service and the obtained container information of the kubernets cluster, a dns monitoring service of the Coredns is started, so that when the Coredns monitors a dns resolution request of the kubernets service sent by a target Pod, a dns resolution request of the kubernets service sent by the target Pod is received.
S406: and receiving a dns resolution request of the kubernets service sent by the target Pod.
S407: and acquiring the IP address corresponding to the target Pod based on the dns resolution request of the kubernets service.
In the process of specifically executing step S406 to step S407, the specific execution process and implementation principle of step S406 to step S407 are the same as the specific execution process and implementation principle of step S301 to step S302 shown in fig. 3 disclosed in the above embodiment of the present invention, and reference may be made to corresponding parts in fig. 3 disclosed in the above embodiment of the present invention, which is not described again here.
S408: judging whether the IP address is the IP address corresponding to any Pod in the kubernets cluster or not; if the IP address is not the IP address corresponding to any Pod in the kubernets cluster, execute step S409; if the IP address is the IP address corresponding to any Pod in the kubernets cluster, step S411 is executed.
In the embodiment of the application, under the condition that the network configuration of the kubernets cluster is determined to be an overlay network, whether the IP address belongs to a network segment in network segment information of the overlay network is judged; if the IP address does not belong to the network segment in the network segment information of the overlay network, determining that the IP address is not the IP address corresponding to the Pod in the kubernets cluster, and further determining that the target Pod is not the Pod in the kubernets cluster; if the IP address belongs to the network segment in the network segment information of the overlay network, determining that the IP address is the IP address corresponding to the Pod container in the kubernets cluster, and further determining that the target Pod container is the Pod container in the kubernets cluster.
S409: determining that the target Pod is not a Pod within the kubernets cluster. And resolving the domain name of the kubernets service in the kubernets cluster into an external IP based on the hybrid plug-in.
S410: and sending the external IP to the target Pod so that the target Pod establishes connection with the kubernets service based on the external IP.
S411: and determining that the target Pod is a Pod in the kubernets cluster, and resolving the domain name of the kubernets service in the kubernets cluster into a cluster IP based on the hybrid plug-in.
S412: and sending the cluster IP to the target Pod so that the target Pod establishes connection with the kubernets service based on the cluster IP.
In the process of specifically executing step S409 to step S412, the specific execution process and implementation principle of step S409 to step S412 are the same as the specific execution process and implementation principle of step S304 to step S307 shown in fig. 3 disclosed in the above embodiment of the present invention, and reference may be made to corresponding parts in fig. 3 disclosed in the above embodiment of the present invention, which is not described again here.
In this embodiment of the application, when a network of a kubernets cluster is configured as an overlay network, coredns may start a dns monitoring service of itself based on acquired domain name information of kubernets service and network segment information of the overlay network, so that when the coredns monitors a dns resolution request of kubernets service sent by a target Pod, a dns resolution request of the kubernets service sent by the target Pod is received; when the network of the kubernets cluster is configured as an underlay network, the registers can start own dns monitoring service based on the obtained domain name information of the kubernets service and the container information of the kubernets cluster, so that when the registers monitors a dns resolution request of the kubernets service sent by a target Pod, the registers receives the dns resolution request of the kubernets service sent by the target Pod.
For a better understanding of the above, the following examples are given.
For example, as shown in FIG. 5, a cluster of kubernets-1 (k8s-1) has a Pod container, an APIServer (kubernets APIServer in this application), and coredns with a hybrid plug-in deployed. A Pod container is deployed in a kubernets-2 cluster (k8s-2), wherein the domain name information of the kubernets service comprises cluster IP: 10.10.1.2 and external IP: 192.168.0.58, IP address of Pod container deployed in kubernets-1 cluster (k8s-1) is 10.244.0.1; the IP address of the Pod container deployed in the kubernets-2 cluster (k8s-2) is 10.10.0.1. The Pod container corresponding to the VM has an IP address of 10.10.0.3.
If the network of the kubernets cluster is configured as an overlay network, after the dns starts its own dns monitoring service according to domain name information of the kubernets service and network segment information (10.244.0.0/16) of the overlay network, if a dns resolution request of the kubernets service sent by the target Pod, acquiring the IP address of the target Pod container as (10.10.0.1) according to the received dns resolution request of the kubernets service; according to the acquired IP address and network segment information of the overlay network, the target Pod can be determined not to be a Pod in the kubernets-1 cluster, and then the domain name of the kubernets service in the kubernets-1 cluster is analyzed to be an externaliIP based on the hybrid plug-in: 192.168.0.58, respectively; and according to the IP address of the target Pod, analyzing data externalilIP: 192.168.0.58 sends the target Pod (Pod containers in the kubernets-2 cluster (k8 s-2)) so that the target Pod, upon receiving the externalIP returned by coredns: 192.168.0.58, the data may be encoded according to the externalIP: 192.168.0.58 establishes connection with kubernets service, and then can access kubernets service.
If the dns resolution request of the kubernets service sent by the target Pod, acquiring the IP address of the target Pod as (10.244.0.1) according to the received dns resolution request of the kubernets service; according to the acquired IP address and network segment information of the overlay network, the target Pod can be determined to be a Pod in the kubernets-1 cluster, and then the kubernets service domain name in the kubernets-1 cluster is analyzed to be a cluster IP based on the hybrid plug-in: 10.10.1.2, respectively; and resolving data cluster IP according to the IP address of the target Pod: 10.10.1.2 sends the Pod containers in the target Pod-1 cluster (k8s-1) so that the target Pod containers, upon receiving the clusterIP returned by coredns: 10.10.1.2, the data may be written according to cluster IP: 10.10.1.2 establishes connection with kubernets service, and then can access kubernets service.
Based on the domain name resolution method disclosed by the embodiment of the invention, the embodiment of the invention also correspondingly discloses a domain name resolution device, which is applied to coredns deployed in a kubernets cluster, wherein hybrid plug-ins are deployed in the coredns, and the coredns is connected with kubernets APIServers in the kubernets cluster, as shown in fig. 6, the domain name resolution device comprises:
a receiving unit 61, configured to receive a dns resolution request of a kubernetes service sent by a target Pod;
a first obtaining unit 62, configured to obtain an IP address corresponding to the target Pod based on a dns resolution request of the kubernets service;
a first judging unit 63, configured to judge whether an IP address is an IP address corresponding to any Pod in a kubernetes cluster;
the first parsing unit 64 is configured to determine that the target Pod is not a Pod in the kubernets cluster if the IP address is not an IP address corresponding to any Pod in the kubernets cluster. Analyzing the domain name of the kubernets service in the kubernets cluster into an external IP based on the hybrid plug-in;
a first sending unit 65, configured to send an external IP to the target Pod, so that the target Pod establishes a connection with the kubernets service based on the external IP.
The specific principle and the execution process of each unit in the domain name resolution device disclosed in the above embodiment of the present invention are the same as those of the domain name resolution method disclosed in the above embodiment of the present invention, and reference may be made to the corresponding parts in the domain name resolution method disclosed in the above embodiment of the present invention, and details are not repeated here.
The invention provides a domain name resolution device, which is applied to coredns deployed in a kubernets cluster, wherein a hybrid plug-in is deployed in the coredns deployed in the kubernets cluster, and connection between the coredns and kubernets APIServers in the kubernets cluster is established, so that after receiving a dns resolution request of kubernets service sent by a target Pod, the coredns obtains an IP address corresponding to the target Pod based on the dns resolution request of the kubernets service; judging whether the IP address is the IP address corresponding to any Pod in the kubernetes cluster or not; under the condition that the IP address is not the IP address corresponding to any Pod in the kubernets cluster, determining that the target Pod is not any Pod in the kubernets cluster, and analyzing the Kubernets service domain name in the kubernets cluster into an external IP based on a hybrid plug-in; and sending the external IP to the target Pod, so that the target Pod establishes connection with the kubernets service based on the external IP. According to the technical scheme provided by the invention, the hybrid plug-in is deployed in the coredns deployed in the kubernets cluster, so that the kubernets service domain name in the kubernets cluster is analyzed into the external IP directly on the basis of the hybrid plug-in under the condition that the target Pod is determined not to be any Pod container in the kubernets cluster, and one external coredns does not need to be deployed in the kubernets cluster, so that the use of hardware resources is reduced, and the cost is reduced.
Further, the domain name resolution device provided by the present invention further includes:
the second analysis unit is used for determining that the target Pod is a Pod in the kubernets cluster if the IP address is the IP address corresponding to any Pod in the kubernets cluster, and analyzing the domain name of the kubernets service in the kubernets cluster into a cluster IP based on the hybrid plug-in;
and the second sending unit is used for sending the cluster IP to the target Pod so that the target Pod establishes connection with the kubernets server based on the cluster IP.
Further, the domain name resolution device provided by the present invention further includes:
the monitoring unit is used for monitoring and caching domain name information of the kubernets service by using the coredns, wherein the domain name information of the kubernets service comprises a cluster IP and an external IP;
the reading unit is used for reading a target configuration file under a preset name space when the network of the kubernets cluster is configured as an overlay network, and acquiring network segment information of the overlay network from the target configuration file;
the second acquisition unit is used for monitoring and acquiring container information of the kubernets cluster when the network of the kubernets cluster is configured as an underlay network, wherein the container information comprises the IP address of each Pod;
and the starting unit is used for starting a dns monitoring service of coredns based on domain name information of the kubernets service and network segment information/kubernets cluster container information of the overlay network, so that when the cosdns monitors a dns resolution request of the kubernets service sent by the target Pod, the dns resolution request of the kubernets service sent by the target Pod is received.
Optionally, if the network of the kubernets cluster is configured as an overlay network, the first determining unit includes:
the second judgment unit is used for judging whether the IP address belongs to a network segment in network segment information of an overlay network or not if the network of the kubernets cluster is configured as the overlay network;
the first determining unit is used for determining that the IP address is not the IP address corresponding to any Pod in the kubernets cluster if the IP address does not belong to the network segment in the network segment information of the overlay network;
and the second determining unit is used for determining that the IP address is the IP address corresponding to the Pod in the kubernets cluster if the IP address belongs to the network segment in the network segment information of the overlay network.
Optionally, if the network of the kubernets cluster is configured as an underlay network, the first determining unit includes:
a third judging unit, configured to judge whether the IP address is an IP address in the container information if the network of the kubernets cluster is configured as an underlay network;
a third determining unit, configured to determine that the IP address is not an IP address corresponding to any Pod in the kubernets cluster if the IP address is not an IP address in the container information;
and the fourth determining unit is used for determining that the IP address is the IP address corresponding to any Pod in the kubernets cluster if the IP address is the IP address in the container information.
An electronic device according to an embodiment of the present application is provided, as shown in fig. 7, the electronic device includes a processor 701 and a memory 702, where the memory 702 is configured to store program codes and data for domain name resolution, and the processor 701 is configured to call program instructions in the memory to execute steps that are implemented in the domain name resolution method according to the above embodiment.
The embodiment of the present application provides a storage medium, where the storage medium includes a storage program, and when the program runs, a device in which the storage medium is located is controlled to execute the domain name resolution method shown in the above embodiment.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, the system or system embodiments are substantially similar to the method embodiments and therefore are described in a relatively simple manner, and reference may be made to some of the descriptions of the method embodiments for related points. The above-described system and system embodiments are merely illustrative, wherein units described as separate components may or may not be physically separate, and components shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
The foregoing is only a preferred embodiment of the present invention, and it should be noted that it is obvious to those skilled in the art that various modifications and improvements can be made without departing from the principle of the present invention, and these modifications and improvements should also be considered as the protection scope of the present invention.

Claims (10)

1. A domain name resolution method is applied to coredns deployed inside a kubernets cluster, wherein hybrid plug-ins are deployed inside the coredns, and the coredns establishes connection with kubernets APIServer inside the kubernets cluster, and the method comprises the following steps:
receiving a dns analysis request of kubernets service sent by a target Pod;
acquiring an IP address corresponding to the target Pod based on the dns resolution request of the kubernets service;
judging whether the IP address is the IP address corresponding to any Pod container in the kubernetes cluster or not;
if the IP address is not the IP address corresponding to any Pod container in the kubernets cluster, determining that the target Pod container is not the Pod container in the kubernets cluster, and resolving the domain name of the kubernets service in the kubernets cluster into an external IP based on the hybrid plug-in;
and sending the external IP to the target Pod so that the target Pod establishes connection with the kubernets service based on the external IP.
2. The method of claim 1, further comprising:
if the IP address is the IP address corresponding to any Pod container in the kubernets cluster, determining that the target Pod container is the Pod container in the kubernets cluster, and resolving the kubernets service domain name in the kubernets cluster into a cluster IP based on the hybrid plug-in;
and sending the cluster IP to the target Pod so that the target Pod establishes connection with the kubernets service based on the cluster IP.
3. The method of claim 1, wherein before receiving a dns resolution request for a kubernets service sent by a target Pod, the method further comprises:
the coredns monitors and caches domain name information of the kubernets service, wherein the domain name information of the kubernets service comprises a cluster IP and an external IP;
when the network of the kubernets cluster is configured as an overlay network, reading a target configuration file under a preset namespace, and acquiring network segment information of the overlay network from the target configuration file;
when the network of the kubernets cluster is configured as an underlay network, monitoring and acquiring container information of the kubernets cluster, wherein the container information comprises an IP address of each Pod;
based on the domain name information of the kubernets service and the network segment information/the kubernets cluster container information of the overlay network, starting dns monitoring service of the coedns, so that when the coedns monitors a dns resolution request of the kubernets service sent by the target Pod, the dns resolution request of the kubernets service sent by the target Pod is received.
4. The method of claim 3, wherein if the network of the kubernets cluster is configured as the overlay network, the determining whether the IP address is an IP address corresponding to any Pod container in the kubernets cluster comprises:
if the network of the kubernets cluster is configured as the overlay network, judging whether the IP address belongs to a network segment in network segment information of the overlay network;
if the IP address does not belong to the network segment in the network segment information of the overlay network, determining that the IP address is not the IP address corresponding to any Pod in the kubernets cluster;
if the IP address belongs to the network segment in the network segment information of the overlay network, determining that the IP address is the IP address corresponding to the Pod container in the kubernets cluster.
5. The method of claim 3, wherein if the network of the kubernets cluster is configured as the underlay network, the determining whether the IP address is an IP address corresponding to any Pod container within the kubernets cluster comprises:
if the network of the kubernets cluster is configured as the underlay network, judging whether the IP address is the IP address in the container information;
if the IP address is not the IP address in the container information, determining that the IP address is not the IP address corresponding to any Pod container in the kubernets cluster;
and if the IP address is the IP address in the container information, determining that the IP address is the IP address corresponding to any Pod container in the kubernets cluster.
6. A domain name resolution apparatus, applied to coredns deployed inside a kubernets cluster, wherein hybrid plug-ins are deployed inside the coredns, and the coredns has established connection with kubernets apis server within the kubernets cluster, the apparatus comprising:
the receiving unit is used for receiving a dns resolution request of the kubernets service sent by the target Pod;
a first obtaining unit, configured to obtain, based on the dns resolution request of the kubernets service, an IP address corresponding to the target Pod;
a first judging unit, configured to judge whether the IP address is an IP address corresponding to any Pod in the kubernetes cluster;
a first parsing unit, configured to determine that the target Pod is not a Pod in the kubernets cluster if the IP address is not an IP address corresponding to any Pod in the kubernets cluster, and parse a domain name of the kubernets service in the kubernets cluster into an external IP based on the hybrid plug-in;
a first sending unit, configured to send the external IP to the target Pod, so that the target Pod establishes a connection with the kubernets service based on the external IP.
7. The apparatus of claim 6, wherein the apparatus comprises:
a second parsing unit, configured to determine that the target Pod is the Pod in the kubernets cluster if the IP address is an IP address corresponding to any one of the Pod containers in the kubernets cluster, and parse a domain name of the kubernets service in the kubernets cluster into a clusterIP based on the hybrid plug-in;
and the second sending unit is used for sending the clusterIP to the target Pod container so that the target Pod container establishes connection with the kubernets service based on the clusterIP.
8. The apparatus of claim 6, wherein prior to executing the receiving unit, the apparatus further comprises:
a monitoring unit, configured to monitor and cache domain name information of the kubernets service in the coredns, where the domain name information of the kubernets service includes clusterIP and externalIP;
the reading unit is used for reading a target configuration file under a preset name space when the network of the kubernets cluster is configured as an overlay network, and acquiring network segment information of the overlay network from the target configuration file;
a second obtaining unit, configured to monitor and obtain container information of the kubernets cluster when a network of the kubernets cluster is configured as an underlay network, where the container information includes an IP address of each Pod;
a starting unit, configured to start a dns monitoring service of the coredns based on domain name information of the kubernets service and network segment information of an overlay network/the kubernets cluster container information, so that when a dns resolution request of the kubernets service sent by the target Pod is monitored by the coredns, the dns resolution request of the kubernets service sent by the target Pod is received.
9. An electronic device, comprising a processor and a memory, the memory storing program code and data for domain name resolution, the processor being configured to invoke program instructions in the memory to perform the domain name resolution method of any of claims 1-5.
10. A storage medium, characterized in that the storage medium comprises a storage program, wherein when the program runs, a device in which the storage medium is located is controlled to execute the domain name resolution method according to any one of claims 1 to 5.
CN202110976814.9A 2021-08-24 2021-08-24 Domain name resolution method and device, electronic equipment and storage medium Active CN113691647B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110976814.9A CN113691647B (en) 2021-08-24 2021-08-24 Domain name resolution method and device, electronic equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110976814.9A CN113691647B (en) 2021-08-24 2021-08-24 Domain name resolution method and device, electronic equipment and storage medium

Publications (2)

Publication Number Publication Date
CN113691647A true CN113691647A (en) 2021-11-23
CN113691647B CN113691647B (en) 2024-01-16

Family

ID=78582073

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110976814.9A Active CN113691647B (en) 2021-08-24 2021-08-24 Domain name resolution method and device, electronic equipment and storage medium

Country Status (1)

Country Link
CN (1) CN113691647B (en)

Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180019968A1 (en) * 2016-07-13 2018-01-18 DNSthingy Inc. Method and router to permit or block internet protocol (ip) connectivity based on originating domain name server (dns) requests
CN107707688A (en) * 2017-10-19 2018-02-16 杭州数梦工场科技有限公司 A kind of method and device of kubernetes clusters parsing host host name
US20190222553A1 (en) * 2016-11-17 2019-07-18 Tencent Technology (Shenzhen) Company Limited Method, device and system for service platform address resolution
CN110086895A (en) * 2019-04-11 2019-08-02 天津字节跳动科技有限公司 Domain name analytic method, device, medium and electronic equipment
CN110611697A (en) * 2019-08-02 2019-12-24 杭州网银互联科技股份有限公司 Network architecture and network deployment method of hybrid cloud
CN111800458A (en) * 2020-05-22 2020-10-20 浙商银行股份有限公司 Dynamic load balancing method and system for Kubernetes container cloud platform
CN111866206A (en) * 2020-06-24 2020-10-30 北京金山云网络技术有限公司 Distributed domain name resolution method, device and equipment
WO2021017279A1 (en) * 2019-07-30 2021-02-04 平安科技（深圳）有限公司 Cluster security management method and apparatus based on kubernetes and network domain, and storage medium
CN112671860A (en) * 2020-12-15 2021-04-16 杭州溪塔科技有限公司 Service access method, system, electronic device and medium for kubernets cluster

Patent Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180019968A1 (en) * 2016-07-13 2018-01-18 DNSthingy Inc. Method and router to permit or block internet protocol (ip) connectivity based on originating domain name server (dns) requests
US20190222553A1 (en) * 2016-11-17 2019-07-18 Tencent Technology (Shenzhen) Company Limited Method, device and system for service platform address resolution
CN107707688A (en) * 2017-10-19 2018-02-16 杭州数梦工场科技有限公司 A kind of method and device of kubernetes clusters parsing host host name
CN110086895A (en) * 2019-04-11 2019-08-02 天津字节跳动科技有限公司 Domain name analytic method, device, medium and electronic equipment
WO2021017279A1 (en) * 2019-07-30 2021-02-04 平安科技（深圳）有限公司 Cluster security management method and apparatus based on kubernetes and network domain, and storage medium
CN110611697A (en) * 2019-08-02 2019-12-24 杭州网银互联科技股份有限公司 Network architecture and network deployment method of hybrid cloud
CN111800458A (en) * 2020-05-22 2020-10-20 浙商银行股份有限公司 Dynamic load balancing method and system for Kubernetes container cloud platform
CN111866206A (en) * 2020-06-24 2020-10-30 北京金山云网络技术有限公司 Distributed domain name resolution method, device and equipment
CN112671860A (en) * 2020-12-15 2021-04-16 杭州溪塔科技有限公司 Service access method, system, electronic device and medium for kubernets cluster

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
石恩名;肖晓军;卢宇;: "基于云平台的分布式高性能网络爬虫的研究与设计", 电信科学, no. 08 *

Also Published As

Publication number Publication date
CN113691647B (en) 2024-01-16

Similar Documents

Publication Publication Date Title
CN109547570B (en) Service registration method, device, registration center management equipment and storage medium
CN108156210B (en) Target resource acquisition method and device
CN107635027B (en) Domain name resolution method, medium, device and computing equipment
CN105897947B (en) The Network Access Method and device of mobile terminal
CN112989330B (en) Container intrusion detection method, device, electronic equipment and storage medium
CN106657434B (en) method and device for checking IP address
CN110968356B (en) Method and device for acquiring configuration information
CN110830606A (en) Method and device for solving abnormal DNS cache and computer readable storage medium
CN114205342A (en) Routing method, electronic device, medium, and program product for service debugging
CN113923008B (en) Malicious website interception method, device, equipment and storage medium
CN115086208A (en) Network card detection method and device, electronic equipment and storage medium
CN112162873B (en) Remote calling method, electronic device and storage medium
CN109788251A (en) Method for processing video frequency, device and storage medium
CN110661673A (en) Heartbeat detection method and device
CN108011801B (en) Data transmission method, equipment, device and system
CN106790071B (en) Method and device for detecting DNS full-flow hijacking risk
CN113014573A (en) Monitoring method, system, electronic device and storage medium of DNS (Domain name Server)
CN113691647B (en) Domain name resolution method and device, electronic equipment and storage medium
CN107547674A (en) Address distribution method and device
CN114553771B (en) Method for virtual router loading and related equipment
CN115801653A (en) Network detection method, system, electronic device and readable storage medium
CN112702441B (en) Container-based access data processing method, device, system and storage medium
CN114356456A (en) Service processing method, device, storage medium and electronic equipment
CN115333993A (en) Method, equipment and storage medium for customizing container group routing in container environment
CN114938396A (en) Routing method of service call request, method and device for creating service

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant