CN116405462A

CN116405462A - Domain name resolution method, container service system, computing device and storage medium

Info

Publication number: CN116405462A
Application number: CN202310670797.5A
Authority: CN
Inventors: 张百合
Original assignee: Alibaba China Co Ltd
Current assignee: Alibaba China Co Ltd
Priority date: 2023-06-07
Filing date: 2023-06-07
Publication date: 2023-07-07
Anticipated expiration: 2043-06-07
Also published as: CN116405462B

Abstract

In the embodiment of the application, by simplifying the corresponding relation between the domain name resolution configuration file and the space name of the service name and the name space of the service object maintained by the domain name service component, the containerized application is further supported to only provide the service name of the service object required to be accessed, the same name space and the cross-name space access to the service object can be realized, the domain name rule of the containerized application to access the service object is greatly simplified, the domain name resolution times are reduced, the domain name resolution time is shortened, and the probability of the service access overtime situation is reduced.

Description

Domain name resolution method, container service system, computing device and storage medium

Technical Field

The present disclosure relates to the field of computer technologies, and in particular, to a domain name resolution method, a container service system, a computing device, and a storage medium.

Background

In the Kubernetes (K8 s) scenario, a containerized application in a container group (Pod) may access Service objects (services) across namespaces (namespaces), i.e., service objects in other namespaces than the namespace to which the container group belongs. Currently, accessing a service object across namespaces may require multiple attempts of domain name resolution, and the overall domain name resolution process is long, which can easily cause service access timeouts.

Disclosure of Invention

Aspects of the present application provide a domain name resolution method, a container service system, a computing device, and a storage medium, which are used to improve domain name resolution efficiency.

The embodiment of the application provides a domain name resolution method, which is applied to a target container group, and comprises the following steps: acquiring first domain name information of a target service object sent by a containerized application, wherein the containerized application is deployed in a target container group and has access requirements on the target service object; inquiring a domain name resolution configuration file corresponding to the target container group to acquire the IP address and domain name suffix configuration information of a target domain name service module configured for the target container group, wherein the domain name suffix addition information indicates that the domain name suffix does not need to be added to the first domain name information; under the indication of the domain name suffix configuration information, a domain name resolution request is sent to a target domain name service component according to the IP address of the target domain name service component, and the domain name resolution request comprises first domain name information; and receiving the IP address of the target service object returned by the target domain name service component so that the containerized application in the target container group can access the target service object according to the IP address of the target service object.

The embodiment of the application also provides a domain name resolution method applied to the target domain name service component, which comprises the following steps: receiving a domain name resolution request sent by a target container group, wherein the domain name resolution request comprises first domain name information of a target service object, and a containerized application in the target container group has access requirements on the target service object; if the first domain name information is the service name of the target service object, inquiring the corresponding relation between the service name of the service object and the space name of the name space to acquire the space name of the name space to which the target service object belongs; the space name of the name space to which the target service object belongs is used as a domain name suffix, and the service name of the target service object and the space name of the name space to which the target service object belongs are spliced to obtain second domain name information; performing domain name resolution on the second domain name information to obtain an IP address of the target service object; and returning the IP address of the target service object to the target container group so that the containerized application in the target container group can access the target service object according to the IP address of the target service object.

Embodiments of the present application also provide a container services system comprising a plurality of namespaces, at least a portion of which deploy at least one of: at least one container group, at least one domain name service component, and at least one service object; the target container group is used for acquiring first domain name information of a target service object sent by the containerized application, the containerized application is deployed in the target container group, and the containerized application has access requirements on the target service object; inquiring a domain name resolution configuration file corresponding to the target container group to acquire the IP address and domain name suffix configuration information of a target domain name service module configured for the target container group, wherein the domain name suffix addition information indicates that the domain name suffix does not need to be added to the first domain name information; under the indication of the domain name suffix configuration information, a domain name resolution request is sent to a target domain name service component according to the IP address of the target domain name service component, and the domain name resolution request comprises first domain name information; receiving an IP address of a target service object returned by the target domain name service component, so that a containerized application in the target container group can access the target service object according to the IP address of the target service object; the target domain name service component is used for receiving a domain name resolution request sent by the target container group; if the first domain name information is the service name of the target service object, inquiring the corresponding relation between the service name of the service object and the space name of the name space to acquire the space name of the name space to which the target service object belongs; the space name of the name space to which the target service object belongs is used as a domain name suffix, and the service name of the target service object and the space name of the name space to which the target service object belongs are spliced to obtain second domain name information; performing domain name resolution on the second domain name information to obtain an IP address of the target service object; the IP address of the target service object is returned to the target container group.

Embodiments of the present application also provide a computing device, comprising: a memory and a processor; a memory for storing a computer program; the processor is coupled to the memory for executing the computer program for performing the steps in the domain name resolution method.

Embodiments of the present application also provide a computer-readable storage medium storing a computer program, which when executed by a processor, causes the processor to implement steps in a domain name resolution method.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiments of the application and together with the description serve to explain the application and do not constitute an undue limitation to the application. In the drawings:

FIG. 1 is a domain name resolution diagram of the prior art;

fig. 2 is a signaling interaction diagram of a domain name resolution method according to an embodiment of the present application;

FIG. 3 is an exemplary application scenario diagram featuring access of service names as domain names;

FIG. 4 is another exemplary application scenario diagram featuring access to service names and space names as domain names;

fig. 5 is a flowchart of a domain name resolution method provided in an embodiment of the present application;

FIG. 6 is a flowchart of another domain name resolution method according to an embodiment of the present application;

fig. 7 is a schematic structural diagram of a computing device according to an embodiment of the present application.

Detailed Description

For the purposes, technical solutions and advantages of the present application, the technical solutions of the present application will be clearly and completely described below with reference to specific embodiments of the present application and corresponding drawings. It will be apparent that the described embodiments are only some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.

In embodiments of the present application, "at least one" means one or more, and "a plurality" means two or more. "and/or" describes the access relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may represent: there are three cases, a alone, a and B together, and B alone, wherein a, B may be singular or plural. In the text description of the present application, the character "/" generally indicates that the front-rear association object is an or relationship. In addition, in the embodiments of the present application, "first", "second", "third", etc. are only for distinguishing the contents of different objects, and have no other special meaning.

Some terms involved in the embodiments of the present application are explained below:

k8s: is an open-source container orchestration engine, supporting automated deployment and management of containerized applications.

Namespaces (namespaces): resources in the same cluster are divided into groups that are isolated from each other. The resource names within the same namespace are unique, but there is no such requirement across namespaces.

Container service system: refers to a system that provides container application management services, such as those built by various container orchestration engines, such as K8 s.

The container group: comprising a number of containers, is the smallest scheduled resource unit in the container service system. The containers in the container group are automatically arranged on the same physical machine or virtual machine in the cluster and may be scheduled together. In the K8s scenario, the container group is referred to as Pod.

Service object (service): a unified portal address may be provided for a group of container applications having the same functionality and request loads distributed to the individual container applications in the group of containers.

Domain name service (Domain Name Service) component: refers to a component with domain name resolution capability that is capable of converting a domain name to an IP (Internet Protocol ) address.

Fig. 1 is a schematic diagram of domain name resolution in the prior art. Referring to FIG. 1, a container service system includes a plurality of namespaces including, for example, but not limited to: namespace1 (namespace 1), namespace2 (namespace 2), and namespace3 (namespace 3). Where namespace1 deploys a container group and service object named service1, the service object of service1 has an IP address of, for example, 1.1.1.1. Namespace2 deploys a service object with a service name of service2, with an IP address of service2, e.g., 2.2.2.2. Namespace3 deploys a domain name service component having an IP address of, for example, 3.3.3.3.

Assuming that the object name of the service object is denoted as service-name, the space name of the namespace to which the service object belongs is denoted as namespace-name. Currently, the rules for containerized applications to access service objects are: if the service objects of the same name space are accessed, the object names of the service objects are used as domain names of the service objects, namely, the service-name is used for access. If the service objects of different namespaces are accessed, the object names of the service objects and the space names of the namespaces are used as domain names of the service objects, namely, the service-name.

In practical application, when there is a need to access a service object, the containerized application sends domain name information of the service object to a container group deployed by the containerized application, the container group requests the domain name service component to conduct domain name resolution according to a domain name resolution configuration file associated with the container group, and an IP address of the service object returned by the domain name service component is provided to the containerized application, so that the containerized application accesses the service object according to the IP address of the service object.

The domain name resolution profile typically configures the IP address, search domain, and domain name suffix configuration information of the domain name service component. Wherein the search field is used to define a search listing of domain names. The domain name suffix configuration information constrains the number of domain names included in the domain name information to be resolved. In general, the domain names in the complete domain name information are divided by english periods "," and the number of "," in the domain name information to be resolved, that is, the number of domain names is configured by the domain name suffix configuration information.

In practical application, if the number of the domain names in the domain name information of the service object sent by the containerized application does not accord with the domain name suffix configuration information, the container group sequentially takes the domain names in the search list as the domain name suffixes of the domain name information of the service object sent by the containerized application according to the search sequence of each domain name in the search list, combines the domain name information of the service object sent by the containerized application with the domain names in the search list to obtain a new domain name, and requests the domain name service component to conduct domain name resolution on the new domain name.

Taking the example that the domain name resolution profile is the/etc/resolv.conf file in the K8s scenario, referring to fig. 1, the name server field is used to describe the IP address of the domain name service component, for example, the IP address of the domain name service component is 3.3.3.3. The search field is used to define a search list of domain names, and the search list includes, for example, domain names such as Namespace1.Svc. Cluster. Local, and the like in order. The options names field is used for configuration information of the domain name suffix, for example, the domain name information to be resolved needs to include at least 5 domain names.

Several specific domain name resolution scenarios are presented below:

scene 1:

if the containerized application deployed in the container group of the namespace1 needs to access the service1 service object in the same namespace, the containerized application sends the service name of the service1 service object as domain name information of the service1 service object to the container group, the container group queries the domain name resolution configuration file to obtain an IP address of the domain name resolution component after receiving the service name of the service1 service object, and determines that the domain name in the first request information is service1.Namespace1.Svc.cluster. Local, and the domain name in the first request information is obtained by combining the service name of the service1 service object and the namespace1.Svc.cluster name in the search list, where the first request information is that the container group initiates a domain name resolution request to the domain name resolution component for the first time. Because the first request information correctly indicates that the service1 service object is located in the namespace1, the domain name resolution component can successfully resolve the domain name information in the first request information, obtain the IP address of the service1 service object, and return the IP address of the service1 service object to the container group of the namespace1, where as shown in fig. 1, the response information returned by the domain name resolution component to the container group includes the IP address (i.e. 1.1.1.1) of the service1 service object. Because the IP address of the service1 service object is successfully analyzed, the container group does not need to initiate a new domain name resolution request to the domain name resolution component again, and the domain name resolution task is ended, so that the containerized application can access the service1 service object according to the IP address of the service1 service object.

Scene 2:

if the containerized application deployed in the container group of the namespace1 needs to access the service2 service objects in different namespaces (for example, the namespaces 2), the containerized application sends service2. Naspace 2 domain name information corresponding to the service2 service objects to the container group, after receiving the service2. Naspace 2 domain name information, the container group queries the domain name resolution configuration file to obtain an IP address of the domain name resolution component, and determines that a domain name in the first request information is service2. Naspace 2.Svc. Local, and a domain name in the first request information is obtained by combining the service2. Naspace 2 domain name information with a naspace 1.Svc. Local domain name in the search list according to a search field and a domain name suffix configuration information field options. Since the first request information cannot correctly indicate the namespace of the service object of service2, the domain name resolution component fails to resolve the domain name information in the first request information. Next, the container group determines that the domain name in the second request information is service2.namespace2.svc. Because the second request information correctly indicates that the service2 service object is located in the namespace2, the domain name resolution component can successfully resolve the domain name information in the second request information, obtain the IP address of the service2 service object, and return the IP address of the service2 service object to the container group of the namespace1. Because the IP address of the service2 service object is successfully resolved, the container group does not need to initiate a new domain name resolution request to the domain name resolution component again, and the domain name resolution task is ended, so that the containerized application can access the service2 service object across namespaces according to the IP address of the service2 service object.

Scene 3:

if the containerized application deployed in the container group of the namespace1 needs to access the service2 service object in a different namespace (for example, a namespace 2), the containerized application sends service2. Nav.sc.cluster.local domain name information corresponding to the service2 service object to the container group, and after receiving the service2. Nav.sc.cluster.local domain name information, the container group queries the domain name resolution configuration file to obtain an IP address of the domain name resolution component, and determines that the domain name in the first request information is service2. Nav.space 2. Svc.cluster.local.cluster.local.local. If the domain name resolution component fails to resolve the domain name information in the first request information, the container group determines that the domain name in the second request information is service2.namespace2.svc.cluster.local.svc.cluster.local. If the domain name resolution component fails to resolve the domain name information in the second request information, the container group determines that the domain name in the third request information is service2.namespace2.svc.cluster.local.cluster.local. If the domain name resolution component fails to resolve the domain name information in the third request information, the container group determines that the domain name in the fourth request information is service2.namespace2.svc.cluster.local. That is, after the container group fails to resolve the previous domain name resolution request, the next domain name resolution request may be determined.

As can be seen from the above, the existing domain name resolution configuration file is complex, and has a large constraint on domain name format, and if the domain name format of the domain name information of the service object to be accessed does not meet the requirement of the domain name resolution configuration file, particularly, the scene of accessing the service object across namespaces, multiple times of domain name resolution may need to be tried, and the whole domain name resolution process is long, so that service access overtime is easily caused.

Based on the above, in the embodiment of the present application, by simplifying the corresponding relationship between the domain name resolution configuration file and the service name of the service object and the space name of the namespace maintained by the domain name service component, the embodiment of the present application provides a method for resolving a domain name, a container service system, a computing device and a storage medium, so as to support the containerized application to access the service object in the same namespace and cross-namespace only by providing the service name of the service object to be accessed, greatly simplify the domain name rule of the containerized application to access the service object, reduce the domain name resolution times, shorten the domain name resolution time, and reduce the probability of occurrence of service access timeout situations.

The following describes in detail the technical solutions provided by the embodiments of the present application with reference to the accompanying drawings.

Fig. 2 is a signaling interaction diagram of a domain name resolution method according to an embodiment of the present application. The method is applied to a container service system, the container service system comprises a plurality of namespaces, at least part of the namespaces are used for arranging a plurality of container groups or a plurality of service objects, the same service objects can be arranged in a plurality of different namespaces, or a certain service object can be arranged in one namespace, and the method is not limited in this regard.

Referring to fig. 2, the method may include the steps of:

201. the target container group acquires first domain name information of a target service object sent by a containerized application, the containerized application is deployed in the target container group, and the containerized application has access requirements on the target service object.

Specifically, a plurality of container groups are deployed in a container service system, and the target container group is one of the plurality of container groups. For any containerized application deployed in the target container group, the containerized application may have access requirements to the service objects deployed in the container service system. The service object that the containerized application needs to access is referred to herein as the target service object. When the containerized application has an access requirement for the target service object, the containerized application provides domain name information of the target service object to the target container group, where the domain name information of the target service object is referred to as first domain name information.

In this embodiment, the containerized application takes the service name of the target service object as the first domain name information. In practice, one or more target service objects may be deployed in a container service system. If the number of the target service objects is 1, the containerization application takes the service name of the target service object as the first domain name information. Assume that the object name of the target service object is denoted as service1, and service1 is taken as the first domain name information.

If the number of the target service objects is multiple, the containerized application takes the space name of the name space to which the target service objects belong as a domain name suffix, and splices the service name of the target service objects and the space name of the name space to which the target service objects belong to obtain first domain name information. Assuming that the object name of the target service object is denoted as service2, service2 is deployed in both namespace2 (i.e., namespace 2) and namespace4 (i.e., namespace 4). If the containerized application accesses service2 in namespace2, then service2.namespace2 is taken as the first domain name information. If the containerized application accesses service4 in namespace4, then service2.namespace4 is taken as the first domain name information.

It should be noted that, in the case where the number of the target service objects is plural, the service name of the target service object may be used as the first domain name information, that is, the first domain name information does not need to carry the space name of the namespace to which the target service object belongs. The first domain name information may also carry a space name of a namespace to which the target service object belongs, which is not limited.

Of course, when the number of the target service objects is plural, compared with the case that the first domain name information does not carry the space name of the name space to which the target service object belongs, the first domain name information carries the space name of the name space to which the target service object belongs, so that the domain name resolution efficiency can be improved and the access requirement of the containerized application can be better met.

In this embodiment, the service name of the service object or the service name of the service object and the space name of the name space to which the service object belongs are used as the domain name information of the service object, so that the domain name information required to be provided by the containerized application is greatly simplified, and the domain name resolution efficiency and accuracy can be improved.

202. The target container group queries a domain name resolution configuration file corresponding to the target container group to obtain the IP address and domain name suffix configuration information of a target domain name service module configured for the target container group, and the domain name suffix addition information indicates that the domain name suffix does not need to be added to the first domain name information.

203. Under the indication of the domain name suffix configuration information, the target container group sends a domain name resolution request to the target domain name service component according to the IP address of the target domain name service component, wherein the domain name resolution request comprises first domain name information.

In this embodiment, each container group is configured with its associated domain name resolution profile. The domain name resolution configuration file provided in this embodiment is simplified compared with the existing domain name resolution configuration file, and only needs to include the IP address of the domain name service module configured for the corresponding container group and the configuration information of the domain name suffix, no search domain is required to be configured, and the configuration information of the domain name suffix indicates that the domain name suffix is not required to be added to the domain name information of the service object provided by the containerized application. In this way, the container group only needs to initiate a domain name resolution request to the domain name service module once, and the domain name information in the initiated domain name resolution request is the domain name information of the service object provided by the containerized application, without modification.

In the present embodiment, the domain name service module configured for the target container group is referred to as a target domain name service module. The target container group queries a domain name resolution configuration file corresponding to the target container group to obtain the IP address and domain name suffix configuration information of a target domain name service module configured for the target container group, and the domain name suffix addition information indicates that the domain name suffix does not need to be added to the first domain name information. Under the indication of the domain name suffix configuration information, the target container group directly sends a domain name resolution request to the target domain name service component according to the IP address of the target domain name service component without modifying the first domain name information, and the domain name resolution request comprises the first domain name information.

204. The target domain name service component receives a domain name resolution request sent by the target container group.

205. If the first domain name information is the service name of the target service object, the target domain name service component queries a correspondence between the service name of the service object and the space name of the namespace to obtain the space name of the namespace to which the target service object belongs.

206. The target domain name service component takes the space name of the name space to which the target service object belongs as a domain name suffix, and splices the service name of the target service object and the space name of the name space to which the target service object belongs to obtain second domain name information.

207. And the target domain name service component carries out domain name resolution on the second domain name information to obtain the IP address of the target service object.

208. The target domain name service component returns the IP address of the target service object to the target container group.

In this embodiment, the target domain name service component maintains the correspondence between the service name of the service object and the space name of the namespace, so that the target domain name service component can determine the space name of the namespace to which the target service object belongs only by including the service name of the target service object in the first domain name information sent by the target container group. Furthermore, the containerized application is supported to only provide the service names of the service objects to be accessed, so that the same namespaces and the service objects accessed across namespaces can be realized.

In this embodiment, when the first domain name information is the service name of the target service object, the target domain name service component queries the correspondence between the service name of the service object and the space name of the namespace to obtain the space name of the namespace to which the target service object belongs, and the target domain name service component uses the space name of the namespace to which the target service object belongs as the domain name suffix, and splices the service name of the target service object and the space name of the namespace to which the service object belongs to obtain the second domain name information. For example, the first domain name information is an object name service1 of the target service object, the space name of the namespace to which the target service object belongs is a namespace1, and then the second domain name information is service1.namespace1, and the service1 domain name and the namespace1 in service1.namespace1 are spliced together by using english periods "," and the namespace1 can be regarded as a domain name suffix of the service1.

In practice, a service object may be deployed in only one namespace, or the same service object may be deployed in multiple namespaces. If multiple namespaces deploy the same target service object, the target domain name service component queries for correspondence between the service name of the service object and the space name of the namespace

The correspondence may be found for the space names of the namespaces to which the target service object belongs. For this case, the space names of the namespaces to which the target service object belongs are used as domain name suffixes, and when the target domain name service component splices the service names of the target service object and the space names of the namespaces to which the service object belongs to obtain the second domain name information, the space names of the target namespaces can be selected from the space names of the namespaces to which the target service object belongs; and splicing the service name of the target service object and the space name of the target name space by taking the space name of the target name space as a domain name suffix to obtain second domain name information. For example, assuming that the object name of the target service object is service2, service2 is deployed in both namespace2 (i.e., namespace 2) and namespace4 (i.e., namespace 4). Namespace2 is selected from the Namespace2 and Namespace4, and the second domain name information is service2.Namespace2.

It will be appreciated that even though multiple namespaces deploy the same service object, it is still possible to support containerized applications to access service objects across namespaces by only providing the service name of the service object for which access is desired.

In this embodiment, after obtaining the second domain name information including the service name of the target service object and the space name of the namespace to which the service object belongs, the target domain name service component performs domain name resolution on the second domain name information to obtain the IP address of the target service object, and returns the IP address of the target service object to the target container group, so that the containerized application in the target container group accesses the target service object according to the IP address of the target service object.

According to the technical scheme provided by the embodiment of the application, the corresponding relation between the service name of the service object and the space name of the name space is maintained by simplifying the domain name resolution configuration file and the domain name service component, so that the containerized application can access the service object with the same name space and the cross-name space only by providing the service name of the service object to be accessed, the domain name rule of the containerized application for accessing the service object is greatly simplified, the domain name resolution times are reduced, the domain name resolution time is shortened, and the probability of overtime service access is reduced.

In some alternative embodiments, the containerized application may also be supported to provide domain name information that is stitched from the service name of the service object and the space name of the namespace to which it belongs. For example, when the number of the target service objects is multiple, the first domain name information carries the space name of the name space to which the target service object belongs, so that the domain name resolution efficiency can be improved, and the access requirement of the containerized application can be better met.

Based on the above, if the first domain name information is obtained by splicing the service name of the target service object and the space name of the name space to which the first domain name information belongs, the target domain name service component performs domain name resolution on the first domain name information to obtain the IP address of the target service object; and returning the IP address of the target service object to the target container group so that the containerized application in the target container group can access the target service object according to the IP address of the target service object.

In some alternative embodiments, the containerized application is also supported to access service objects in various domain name formats, which may be internal service objects in the container service system or external service objects (i.e., service objects not deployed in the container service system), without limitation. In practical application, if the target domain name service component determines that the first domain name information is not the service name of the target service object, and is not the domain name information obtained by splicing the service name of the target service object and the space name of the name space to which the service name belongs, the target domain name service component may match the domain name suffix in the first domain name information with the preconfigured domain name suffix of the service object belonging to the inside of the container service system. If the domain name suffix of the service object belonging to the inside of the container service system appears in the first domain name information, determining that the service object corresponding to the first domain name information is the service object of the inside of the container service system if the domain name suffix of the service object belonging to the inside of the container service system appears in the first domain name information, and at this time, performing domain name resolution on the first domain name information according to the domain name access rule of the service object of the inside of the container service system. If the domain name suffix of the service object belonging to the inside of the container service system does not appear in the first domain name information, determining that the service object corresponding to the first domain name information is an external service object, and at this time, performing domain name resolution on the first domain name information according to the domain name access rule of the external service object. The domain name access rule of the service object inside the container service system and the domain name access rule of the external service object can be flexibly set as required, and the method is not limited.

For example, it is assumed that the domain name suffixes of the service objects belonging to the inside of the container service system are respectively cluster, in-addr, arpa, ip6.Arpa, and if the domain name suffixes of the first domain name information include one or more of cluster, in-addr, arpa, ip6.Arpa, the service object corresponding to the first domain name information is the service object of the inside of the container service system. If the domain name suffix of the first domain name information does not include one or more of cluster, in-addr, arpa and ip6.Arpa, the service object corresponding to the first domain name information is an external service object.

The following description is made in connection with the application scenario diagrams shown in fig. 3 and 4.

In fig. 3, the containerized application in the container group accesses the service object using the service name of the service object as the domain name of the service object.

In one scenario, the containerized applications in a container group access service objects in the same namespace. Specifically, when the containerized application in the container group needs to access the service1 service object, the container group obtains the service1 sent by the containerized application, and queries the domain name resolution configuration text to obtain the IP address (3.3.3.3) and the domain name suffix configuration information (options types: 0) of the domain name service component. After determining that no domain name suffix is required to be added behind the service1 according to the domain name suffix configuration information (options candidates: 0), the container group sends a domain name resolution request to the domain name service component according to the IP address of the domain name service component, wherein the request information of the domain name resolution request only comprises the service1; the domain name service component responds to the domain name resolution request, determines that the space name of the name space to which the service1 belongs is a name space1 according to the corresponding relation between the service name of the service object and the space name of the name space, and splices the service1 and the name space1 to obtain a new domain name service1. The domain name service component analyzes the new domain name service1.Namespace1 to obtain the IP address (1.1.1.1) of the service1, and sends response information of the domain name analysis request to the container group so that the containerized application in the container group can access the service1 service object according to the IP address of the service1.

In another scenario, a containerized application in a container group accesses service objects in different namespaces. Specifically, when the containerized application in the container group needs to access the service2 service object, the container group acquires the service2 sent by the containerized application, and queries the domain name resolution configuration text to acquire the IP address (3.3.3.3) and the domain name suffix configuration information (options types: 0) of the domain name service component. After determining that no domain name suffix is required to be added behind the service2 according to the domain name suffix configuration information (options candidates: 0), the container group sends a domain name resolution request to the domain name service component according to the IP address of the domain name service component, wherein the request information of the domain name resolution request only comprises the service2; the domain name service component responds to the domain name resolution request, determines the IP address (2.2.2.2) of the service2 according to the corresponding relation between the service name of the service object and the space name of the name space, and sends the response information of the domain name resolution request to the container group so that the containerized application in the container group can access the service2 service object according to the IP address of the service2.

In FIG. 4, the containerized application in the container group accesses the service object using the service name of the service object and the space name of the namespace to which it belongs as domain names for the service object. Referring to FIG. 4, both namespace2 and namespace4 deploy service2. When a containerized application in a container group needs to access a service2 service object in namespace2 or namespace4, the container group obtains service2.naspace 2 or service4.naspace 4 sent by the containerized application and queries a domain name resolution configuration file to obtain the IP address (3.3.3.3) and domain name suffix configuration information (options nodes: 0) of the domain name service component. After determining that no domain name suffix is required to be added behind the service2 according to the domain name suffix configuration information (options candidates: 0), the container group sends a domain name resolution request to the domain name service component according to the IP address of the domain name service component, wherein the domain name information in the request information of the domain name resolution request is service2.Namespace2 or service4.Namespace4; the domain name service component responds to the domain name resolution request, and because the domain name information in the request information is composed of a service name and a space name, the domain name service component does not need to query the corresponding relation between the service name of the service object maintained locally and the space name of the name space, directly resolves the service2.Namespace2 or the service4.Namespace4 to obtain the IP address (2.2.2.2 or 4.4.4) of the service2, and sends the response information of the domain name resolution request to the container group so that the containerized application in the container group can access the service2 service object in the name space2 according to the IP address of the service2 in the name space2, or the containerized application in the container group can access the service2 service object in the name space4 according to the IP address of the service4 in the name space 4.

Fig. 5 is a flowchart of a domain name resolution method according to an embodiment of the present application. The method is applied to a target container group, which is one of a plurality of container groups deployed in a container service system, see fig. 5, and includes the steps of:

501. and acquiring first domain name information of a target service object sent by the containerized application, wherein the containerized application is deployed in a target container group and has access requirements on the target service object.

502. Inquiring a domain name resolution configuration file corresponding to the target container group to acquire the IP address and domain name suffix configuration information of a target domain name service module configured for the target container group, wherein the domain name suffix addition information indicates that the domain name suffix does not need to be added to the first domain name information.

503. And sending a domain name resolution request to the target domain name service component according to the IP address of the target domain name service component under the indication of the domain name suffix configuration information, wherein the domain name resolution request comprises first domain name information.

504. And receiving the IP address of the target service object returned by the target domain name service component so that the containerized application in the target container group can access the target service object according to the IP address of the target service object.

Further optionally, before acquiring the first domain name information of the target service object sent by the containerization application, the containerization application uses the service name of the target service object as the first domain name information.

Further optionally, when the containerized application uses the service name of the target service object as the first domain name information, the containerized application is specifically configured to: if the number of the target service objects is 1, the containerization application takes the service name of the target service object as the first domain name information.

Further optionally, the method further comprises: if the number of the target service objects is multiple, the containerized application takes the space name of the name space to which the target service objects belong as a domain name suffix, and splices the service name of the target service objects and the space name of the name space to which the target service objects belong to obtain first domain name information.

For the implementation of each step in the embodiment shown in fig. 5, reference may be made to the implementation of each step in the embodiment shown in fig. 2, which is not described herein.

Fig. 6 is a flowchart of another domain name resolution method according to an embodiment of the present application. For application to a target domain name service component, see fig. 6, the method comprises the steps of:

601. and receiving a domain name resolution request sent by the target container group, wherein the domain name resolution request comprises first domain name information of the target service object, and a containerized application in the target container group has access requirements on the target service object.

602. If the first domain name information is the service name of the target service object, the corresponding relation between the service name of the service object and the space name of the name space is queried to acquire the space name of the name space to which the target service object belongs.

603. And splicing the service name of the target service object and the space name of the name space to which the service object belongs by taking the space name of the name space to which the target service object belongs as a domain name suffix to obtain second domain name information.

604. And carrying out domain name resolution on the second domain name information to obtain the IP address of the target service object.

605. And returning the IP address of the target service object to the target container group so that the containerized application in the target container group can access the target service object according to the IP address of the target service object.

Further optionally, if the queried space names of the namespaces to which the target service objects belong are multiple, the space names of the namespaces to which the target service objects belong are used as domain name suffixes, and the service names of the target service objects and the space names of the namespaces to which the service objects belong are spliced to obtain second domain name information, including: selecting a space name of the target namespace from space names of a plurality of namespaces to which the target service object belongs; and splicing the service name of the target service object and the space name of the target name space by taking the space name of the target name space as a domain name suffix to obtain second domain name information.

Further optionally, the method further comprises: if the first domain name information is obtained by splicing the service name of the target service object and the space name of the name space to which the first domain name information belongs, carrying out domain name resolution on the first domain name information to obtain the IP address of the target service object; and returning the IP address of the target service object to the target container group so that the containerized application in the target container group can access the target service object according to the IP address of the target service object.

For the implementation of each step in the embodiment shown in fig. 6, reference may be made to the implementation of each step in the embodiment shown in fig. 2, which is not described herein.

The interaction process of each component in the container service system may refer to the signaling interaction process shown in fig. 2, and will not be described herein.

It should be noted that, the execution subjects of each step of the method provided in the above embodiment may be the same device, or the method may also be executed by different devices. For example, the execution subject of steps 501 to 504 may be device a; for another example, the execution bodies of

steps

501 and 502 may be device a, and the execution bodies of

steps

503 and 504 may be device B; etc.

In addition, in some of the above embodiments and the flows described in the drawings, a plurality of operations appearing in a specific order are included, but it should be clearly understood that the operations may be performed out of the order in which they appear herein or performed in parallel, the sequence numbers of the operations such as 501, 502, etc. are merely used to distinguish between the various operations, and the sequence numbers themselves do not represent any order of execution. In addition, the flows may include more or fewer operations, and the operations may be performed sequentially or in parallel. It should be noted that, the descriptions of "first" and "second" herein are used to distinguish different messages, devices, modules, etc., and do not represent a sequence, and are not limited to the "first" and the "second" being different types.

It should be noted that, the user information (including but not limited to user equipment information, user personal information, etc.) and the data (including but not limited to data for analysis, stored data, presented data, etc.) related to the present application are information and data authorized by the user or fully authorized by each party, and the collection, use and processing of the related data need to comply with the related laws and regulations and standards of the related country and region, and provide corresponding operation entries for the user to select authorization or rejection.

Fig. 7 is a schematic structural diagram of a computing device according to an embodiment of the present application. As shown in fig. 7, the computing device includes: a memory 71 and a processor 72;

memory 71 for storing a computer program and may be configured to store other various data to support operations on the computing platform. Examples of such data include instructions for any application or method operating on a computing platform, contact data, phonebook data, messages, pictures, videos, and the like.

The Memory 71 may be implemented by any type of volatile or non-volatile Memory device or combination thereof, such as Static Random access Memory (Static Random-AccessMemory, SRAM), electrically erasable programmable Read-Only Memory (Electrically Erasable Programmable Read Only Memory, EEPROM), erasable programmable Read-Only Memory (Erasable Programmable Read Only Memory, EPROM), programmable Read-Only Memory (Programmable Read-Only Memory, PROM), read-Only Memory (ROM), magnetic Memory, flash Memory, magnetic or optical disk.

A processor 72 coupled to the memory 71 for executing the computer program in the memory 71 for performing the steps in the domain name resolution method.

Further optionally, as shown in fig. 7, the computing device further includes: communication component 73, display 74, power component 75, audio component 76, and other components. Only some of the components are schematically shown in fig. 7, which does not mean that the computing device only includes the components shown in fig. 7. In addition, the components within the dashed box in FIG. 7 are optional components, and not necessarily optional components, depending on the product form of the computing device.

The detailed implementation process of each action performed by the processor may refer to the related description in the foregoing method embodiment or the apparatus embodiment, and will not be repeated herein.

Accordingly, embodiments of the present application also provide a computer-readable storage medium storing a computer program that, when executed, is capable of implementing the steps of the method embodiments described above that may be performed by a computing device.

Accordingly, embodiments of the present application also provide a computer program product comprising a computer program/instructions which, when executed by a processor, cause the processor to carry out the steps of the above-described method embodiments that are executable by a computing device.

The communication component is configured to facilitate wired or wireless communication between the device in which the communication component is located and other devices. The device where the communication component is located may access a wireless network based on a communication standard, such as a mobile communication network of WiFi (Wireless Fidelity ), 2G (2 generation,2 generation), 3G (3 generation ), 4G (4 generation,4 generation)/LTE (long Term Evolution ), 5G (5 generation,5 generation), or a combination thereof. In one exemplary embodiment, the communication component receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, the communication component further includes a near field communication (Near Field Communication, NFC) module to facilitate short range communications. For example, the NFC module may be implemented based on radio frequency identification (Radio Frequency Identification, RFID) technology, infrared data association (The Infrared Data Association, irDA) technology, ultra Wideband (UWB) technology, bluetooth (BT) technology, and other technologies.

The display includes a screen, which may include a liquid crystal display (Liquid Crystal Display, LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensor may sense not only the boundary of a touch or sliding action, but also the duration and pressure associated with the touch or sliding operation.

The power supply component provides power for various components of equipment where the power supply component is located. The power components may include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for the devices in which the power components are located.

The audio component described above may be configured to output and/or input an audio signal. For example, the audio component includes a Microphone (MIC) configured to receive external audio signals when the device in which the audio component is located is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signal may be further stored in a memory or transmitted via a communication component. In some embodiments, the audio assembly further comprises a speaker for outputting audio signals.

It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-readable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

In one typical configuration, a computing device includes one or more processors (Central Processing Unit, CPUs), input/output interfaces, network interfaces, and memory.

The Memory may include non-volatile Memory in a computer readable medium, random access Memory (Random Access Memory, RAM) and/or non-volatile Memory, etc., such as Read Only Memory (ROM) or flash RAM. Memory is an example of computer-readable media.

Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase Change RAM (PRAM), static Random-Access Memory (SRAM), dynamic Random-Access Memory (Dynamic Random Access Memory, DRAM), other types of Random-Access Memory (Random Access Memory, RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash Memory or other Memory technology, compact disc Read Only Memory (CD-ROM), digital versatile disc (Digital versatile disc, DVD) or other optical storage, magnetic cassettes, magnetic tape storage or other magnetic storage devices, or any other non-transmission medium, operable to store information that may be accessed by the computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises an element.

The foregoing is merely exemplary of the present application and is not intended to limit the present application. Various modifications and changes may be made to the present application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc. which are within the spirit and principles of the present application are intended to be included within the scope of the claims of the present application.

Claims

1. A domain name resolution method, applied to a target set of containers, the method comprising:

acquiring first domain name information of a target service object sent by a containerized application, wherein the containerized application is deployed in a target container group and has access requirements on the target service object;

Inquiring a domain name resolution configuration file corresponding to the target container group to obtain an IP address and domain name suffix configuration information of a target domain name service module configured for the target container group, wherein the domain name suffix addition information indicates that the domain name suffix does not need to be added to the first domain name information;

sending a domain name resolution request to the target domain name service component according to the IP address of the target domain name service component under the indication of the domain name suffix configuration information, wherein the domain name resolution request comprises the first domain name information;

and receiving the IP address of the target service object returned by the target domain name service component so as to enable the containerized application in the target container group to access the target service object according to the IP address of the target service object.

2. The method of claim 1, further comprising, prior to obtaining the first domain name information of the target service object sent by the containerized application:

the containerized application takes the service name of the target service object as the first domain name information.

3. The method of claim 2, wherein the containerizing application having the service name of the target service object as the first domain name information comprises:

And if the number of the target service objects is 1, the containerization application takes the service name of the target service object as the first domain name information.

4. A method according to claim 3, further comprising:

and if the number of the target service objects is multiple, the containerization application uses the space name of the name space to which the target service objects belong as a domain name suffix, and splices the service name of the target service objects and the space name of the name space to which the service objects belong to obtain the first domain name information.

5. A domain name resolution method applied to a target domain name service component, the method comprising:

receiving a domain name resolution request sent by a target container group, wherein the domain name resolution request comprises first domain name information of a target service object, and a containerized application in the target container group has access requirements on the target service object;

if the first domain name information is the service name of the target service object, inquiring the corresponding relation between the service name of the service object and the space name of the name space to acquire the space name of the name space to which the target service object belongs;

The space name of the name space to which the target service object belongs is used as a domain name suffix, and the service name of the target service object and the space name of the name space to which the target service object belongs are spliced to obtain second domain name information;

performing domain name resolution on the second domain name information to obtain an IP address of the target service object;

and returning the IP address of the target service object to the target container group so that the containerized application in the target container group can access the target service object according to the IP address of the target service object.

6. The method of claim 5, wherein if the queried space names of the namespaces to which the target service objects belong are plural, and the space names of the namespaces to which the target service objects belong are used as domain name suffixes, the splicing the service names of the target service objects and the space names of the namespaces to which the service objects belong to obtain the second domain name information includes:

selecting a space name of a target namespace from space names of a plurality of namespaces to which the target service object belongs;

and splicing the service name of the target service object and the space name of the target name space by taking the space name of the target name space as a domain name suffix to obtain second domain name information.

7. The method as recited in claim 5, further comprising:

if the first domain name information is obtained by splicing the service name of the target service object and the space name of the name space to which the service object belongs, carrying out domain name resolution on the first domain name information to obtain the IP address of the target service object;

8. A container services system comprising a plurality of namespaces, at least a portion of the namespaces deploying at least one of: at least one container group, at least one domain name service component, and at least one service object;

the target container group is used for acquiring first domain name information of a target service object sent by a containerized application, the containerized application is deployed in the target container group, and the containerized application has access requirements on the target service object; inquiring a domain name resolution configuration file corresponding to the target container group to obtain an IP address and domain name suffix configuration information of a target domain name service module configured for the target container group, wherein the domain name suffix addition information indicates that the domain name suffix does not need to be added to the first domain name information; sending a domain name resolution request to the target domain name service component according to the IP address of the target domain name service component under the indication of the domain name suffix configuration information, wherein the domain name resolution request comprises the first domain name information; receiving an IP address of the target service object returned by the target domain name service component, so that the containerized application in the target container group can access the target service object according to the IP address of the target service object;

The target domain name service component is used for receiving a domain name resolution request sent by the target container group; if the first domain name information is the service name of the target service object, inquiring the corresponding relation between the service name of the service object and the space name of the name space to acquire the space name of the name space to which the target service object belongs; the space name of the name space to which the target service object belongs is used as a domain name suffix, and the service name of the target service object and the space name of the name space to which the target service object belongs are spliced to obtain second domain name information; performing domain name resolution on the second domain name information to obtain an IP address of the target service object; and returning the IP address of the target service object to the target container group.

9. A computing device, comprising: a memory and a processor; the memory is used for storing a computer program; the processor is coupled to the memory for executing the computer program for performing the steps in the method of any of claims 1-7.

10. A computer readable storage medium storing a computer program, which, when executed by a processor, causes the processor to carry out the steps of the method according to any one of claims 1-7.