CN111182089A

CN111182089A - Container cluster system, method and device for accessing big data assembly and server

Info

Publication number: CN111182089A
Application number: CN201911425208.7A
Authority: CN
Inventors: 关海南; 杜俭峰
Original assignee: Beijing Kingsoft Cloud Network Technology Co Ltd
Current assignee: Beijing Kingsoft Cloud Network Technology Co Ltd
Priority date: 2019-12-31
Filing date: 2019-12-31
Publication date: 2020-05-19
Anticipated expiration: 2039-12-31
Also published as: CN111182089B

Abstract

The invention provides a container cluster system, a method, a device and a server for accessing big data components, wherein the system comprises a container cluster and an out-of-cluster DNS service; the domain name of each node in a big data assembly deployed in a container cluster and an LB address corresponding to each node are recorded in the DNS service outside the cluster; the cluster-outside DNS service is used for analyzing the received first domain name to be accessed to obtain an LB address corresponding to the first domain name to be accessed, and returning the LB address corresponding to the first domain name to be accessed to the application service corresponding to the first domain name to be accessed, so that the application service accesses the node corresponding to the first domain name to be accessed in the big data component through the LB address corresponding to the first domain name to be accessed. By providing an out-of-cluster DNS service outside the container cluster, big data components deployed in the container cluster can provide access services outside the container cluster.

Description

Container cluster system, method and device for accessing big data assembly and server

Technical Field

The invention relates to the technical field of container clustering, in particular to a container clustering system, a method and a device for accessing big data components and a server.

Background

After the application service is deployed in the container cluster, the application service needs to expose an external service interface to the outside, and then access service can be provided to the outside based on the external service interface. However, for the big data component, what the big data component needs to provide externally is not only an external service interface, but also each data node, each computing node, etc. in the component need to be exposed externally; after the big data assembly is deployed in the container cluster, other application services in the container cluster can access each data node, each computing node and the like in the big data assembly through an IP address in the container cluster; however, for application services or application components outside the container cluster, since the IP address inside the container cluster cannot be identified, large data components deployed in the container cluster cannot be accessed, and it is difficult for the large data components deployed in the container cluster to provide access services outside the container cluster.

Disclosure of Invention

In view of this, the present invention provides a container cluster system, and a method, an apparatus, and a server for accessing big data components, so that the big data components deployed in the container cluster can provide access services outside the container cluster.

In a first aspect, an embodiment of the present invention provides a container cluster system, where the system includes a container cluster and an off-cluster domain name system DNS service; a big data component is deployed in the container cluster; the domain name of each node in the big data assembly and the load balancer LB address corresponding to each node are recorded in the cluster external DNS service; the out-of-cluster DNS service is to: analyzing the received first domain name to be accessed to obtain an LB address corresponding to the first domain name to be accessed, and returning the LB address corresponding to the first domain name to be accessed to the application service corresponding to the first domain name to be accessed, so that the application service accesses the node corresponding to the first domain name to be accessed in the big data assembly through the LB address corresponding to the first domain name to be accessed.

With reference to the first aspect, an embodiment of the present invention provides a first possible implementation manner of the first aspect, where a first domain name to be accessed is sent to an out-of-cluster DNS service by an application service outside a container cluster; alternatively, the first domain name to be accessed is sent by the container cluster to an off-cluster DNS service.

With reference to the first aspect, an embodiment of the present invention provides a second possible implementation manner of the first aspect, where an intra-cluster DNS service is also deployed in the container cluster; the cluster DNS service records a domain name and a cluster IP address corresponding to each node in the big data assembly; the domain name of the same node corresponds to the IP address in the cluster; the intra-cluster DNS service is to: and analyzing a second domain name to be accessed sent by the application service in the container cluster to obtain an IP address in the cluster corresponding to the second domain name to be accessed, and returning the IP address in the cluster corresponding to the second domain name to be accessed to the application service in the container cluster, so that the application service in the container cluster accesses a node corresponding to the second domain name to be accessed in the big data component through the IP address in the cluster corresponding to the second domain name to be accessed.

With reference to the second possible implementation manner of the first aspect, an embodiment of the present invention provides a third possible implementation manner of the first aspect, where the intra-cluster DNS service is further configured to: and if the cluster IP address corresponding to the second domain name to be accessed cannot be analyzed, sending the second domain name to be accessed to the cluster external DNS service, so that the second domain name to be accessed is analyzed through the cluster external DNS service, and an LB address corresponding to the second domain name to be accessed is obtained, so that the application service in the container cluster accesses the node corresponding to the second domain name to be accessed in the big data component through the LB address corresponding to the second domain name to be accessed.

With reference to the first aspect, an embodiment of the present invention provides a fourth possible implementation manner of the first aspect, where the system further includes a metadata management service; the metadata management service records the domain name of each node in the big data assembly; the metadata management service is to: the domain names of the nodes in the big data component are provided to application services outside the container cluster or within the container cluster.

With reference to the first aspect, an embodiment of the present invention provides a fifth possible implementation manner of the first aspect, where a cloud management controller component is further deployed in the container cluster; the cloud management controller component is to: creating LB addresses of all nodes in the big data assembly; and sending the domain name of each node in the big data assembly and the LB address of each node in the created big data assembly to the DNS service outside the cluster.

With reference to the fifth possible implementation manner of the first aspect, an embodiment of the present invention provides a sixth possible implementation manner of the first aspect, where the cloud management controller component is further configured to: if the node of the big data assembly has a target node for changing the POD, updating an LB address corresponding to the target node according to the POD changed by the target node; and sending the updated LB address corresponding to the target node to the cluster external DNS service.

In a second aspect, an embodiment of the present invention provides a method for accessing a big data component, where the big data component is deployed in a container cluster; the method is applied to a server; a cluster external DNS service is operated on the server; the domain name and LB address corresponding to each node in the big data assembly are recorded in the cluster external DNS service; the domain name and the LB address of the same node are corresponding to each other; the method comprises the following steps: receiving a domain name to be accessed of a big data component; analyzing the domain name to be accessed through the DNS service outside the cluster to obtain an LB address corresponding to the domain name to be accessed; and returning the LB address corresponding to the domain name to be accessed to the application service corresponding to the domain name to be accessed, so that the application service accesses the node corresponding to the domain name to be accessed in the big data component through the LB address corresponding to the domain name to be accessed.

With reference to the second aspect, an embodiment of the present invention provides a first possible implementation manner of the second aspect, where a domain name to be accessed is sent from an application service outside a container cluster to an out-cluster DNS service; alternatively, the domain name to be accessed is sent by an intra-cluster DNS service in the container cluster to an extra-cluster DNS service.

With reference to the second aspect, an embodiment of the present invention provides a second possible implementation manner of the second aspect, where the method further includes: and receiving the domain name of each node in the big data assembly and the LB address of each node in the created big data assembly, which are sent by the cloud management controller assembly in the container cluster.

In a third aspect, an embodiment of the present invention provides a method for accessing a big data component, where the big data component is deployed in a container cluster; the method is applied to a server; the server runs an intra-cluster DNS service in the container cluster; the cluster DNS service records a domain name and a cluster IP address corresponding to each node in the big data assembly; the domain name of the same node corresponds to the IP address in the cluster; a DNS service outside the cluster is also deployed outside the container cluster; the domain name and LB address corresponding to each node in the big data assembly are recorded in the cluster external DNS service; the domain name and the LB address of the same node are corresponding to each other; the method comprises the following steps: analyzing a domain name to be accessed sent by an application service in the container cluster; if the cluster IP address corresponding to the domain name to be accessed is obtained through analysis, the cluster IP address corresponding to the domain name to be accessed is returned to the application service in the container cluster, so that the application service in the container cluster accesses the node corresponding to the domain name to be accessed in the big data assembly through the cluster IP address corresponding to the domain name to be accessed; and if the cluster IP address corresponding to the domain name to be accessed cannot be analyzed, the domain name to be accessed is sent to the cluster external DNS service, so that the domain name to be accessed is analyzed through the cluster external DNS service, and the LB address corresponding to the domain name to be accessed is obtained, so that the application service in the container cluster accesses the node corresponding to the domain name to be accessed in the big data component through the LB address corresponding to the domain name to be accessed.

In a fourth aspect, an embodiment of the present invention provides an apparatus for accessing a big data component, where the big data component is deployed in a container cluster; the device is arranged on a server; a cluster external DNS service is operated on the server; the cluster external DNS service module records domain names and LB addresses corresponding to each node in the big data assembly; the domain name and the LB address of the same node are corresponding to each other; the device includes: the domain name receiving module to be accessed is used for receiving the domain name to be accessed of the big data assembly; the LB address acquisition module is used for analyzing the domain name to be accessed through the DNS service outside the cluster to obtain an LB address corresponding to the domain name to be accessed; and the LB address returning module is used for returning the LB address corresponding to the domain name to be accessed to the application service corresponding to the domain name to be accessed, so that the application service accesses the node corresponding to the domain name to be accessed in the big data assembly through the LB address corresponding to the domain name to be accessed.

In a fifth aspect, an embodiment of the present invention provides an apparatus for accessing a big data component, where the big data component is deployed in a container cluster; the device is arranged on a server; the server runs an intra-cluster DNS service in the container cluster; the cluster DNS service records a domain name and a cluster IP address corresponding to each node in the big data assembly; the domain name of the same node corresponds to the IP address in the cluster; a DNS service outside the cluster is also deployed outside the container cluster; the domain name and LB address corresponding to each node in the big data assembly are recorded in the cluster external DNS service; the domain name and the LB address of the same node are corresponding to each other; the device includes: the domain name resolution module to be accessed is used for resolving the domain name to be accessed sent by the application service in the container cluster; the in-cluster IP address returning module is used for returning the in-cluster IP address corresponding to the domain name to be accessed to the application service in the container cluster if the in-cluster IP address corresponding to the domain name to be accessed is obtained through resolution, so that the application service in the container cluster accesses the node corresponding to the domain name to be accessed in the big data assembly through the in-cluster IP address corresponding to the domain name to be accessed; and the domain name sending module to be accessed is used for sending the domain name to be accessed to the DNS service outside the cluster if the IP address in the cluster corresponding to the domain name to be accessed cannot be analyzed, so that the domain name to be accessed is analyzed through the DNS service outside the cluster to obtain the LB address corresponding to the domain name to be accessed, and the application service in the container cluster accesses the node corresponding to the domain name to be accessed in the big data component through the LB address corresponding to the domain name to be accessed.

In a sixth aspect, an embodiment of the present invention provides a server, including a processor and a memory, where the memory stores machine executable instructions capable of being executed by the processor, and the processor executes the machine executable instructions to implement the above method for accessing a big data component.

In a seventh aspect, an embodiment of the present invention provides a machine-readable storage medium, where the machine-readable storage medium stores machine-executable instructions, and when the machine-executable instructions are called and executed by a processor, the machine-executable instructions cause the processor to implement the above method for accessing a big data component.

The embodiment of the invention has the following beneficial effects:

the invention provides a container cluster system, a method, a device and a server for accessing big data components, wherein the system comprises a container cluster and an out-cluster DNS service; the domain name and LB address of each node in the big data assembly deployed in the container cluster are recorded in the cluster external DNS service; the domain name and the LB address of the same node are corresponding to each other; the cluster-outside DNS service is used for analyzing the received first domain name to be accessed to obtain an LB address corresponding to the first domain name to be accessed, and returning the LB address corresponding to the first domain name to be accessed to the application service corresponding to the first domain name to be accessed, so that the application service accesses the node corresponding to the first domain name to be accessed in the big data component through the LB address corresponding to the first domain name to be accessed. In the method, the out-cluster DNS service is arranged outside the container cluster, and the domain name and the LB address of each node in the big data assembly are arranged in the out-cluster DNS service, so that the application service outside the container cluster accesses the big data assembly arranged in the container cluster, and the big data assembly arranged in the container cluster can provide access service outside the container cluster.

In addition, the out-of-cluster DNS service can also be used for accessing the big data assembly deployed in the container cluster by the application service in the container cluster and accessing the big data assembly deployed in the container cluster by the application service in other container clusters, so that the consistent stability of the big data assembly service in the container cluster is ensured, and the service quality of the whole container cluster system is improved.

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, and it is obvious that the drawings in the following description are some embodiments of the present invention, and other drawings can be obtained by those skilled in the art without creative efforts.

FIG. 1 is a schematic diagram of a large data component containerization deployment scenario provided by an embodiment of the present invention;

fig. 2 is a schematic structural diagram of a container cluster system according to an embodiment of the present invention;

FIG. 3 is a schematic structural diagram of another container cluster system according to an embodiment of the present invention;

FIG. 4 is a schematic structural diagram of another container cluster system according to an embodiment of the present invention;

FIG. 5 is a flow diagram of a method for accessing big data components according to an embodiment of the present invention;

FIG. 6 is a flow diagram of another method for accessing big data components according to an embodiment of the present invention;

FIG. 7 is a schematic structural diagram of an apparatus for accessing big data components according to an embodiment of the present invention;

FIG. 8 is a schematic structural diagram of another apparatus for accessing big data components according to an embodiment of the present invention;

fig. 9 is a schematic structural diagram of a server according to an embodiment of the present invention.

Detailed Description

The technical solutions of the present invention will be described clearly and completely with reference to the following embodiments, and it should be understood that the described embodiments are some, but not all, embodiments of the present invention. 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.

At present, containerized deployment is a technical trend of a whole IT (Internet Technology ) service background, and referring to fig. 1, a schematic diagram of a large data component containerized deployment scheme is shown, for a general application service, a containerized deployment mode is relatively simple, only one external service needs to be exposed, and the service can be provided in a mode of ingress of k8s and the like. However, for the big data component, containerization deployment is difficult, except that the application service inside the container cluster accesses the big data component, and the cloud host, the physical machine, the bare metal server and the like outside the container cluster may access the big data component. The cloud host, the physical machine, the bare metal server and the like outside the container have the following difficulties when accessing the big data components in the container:

first, the big data component provides services to the outside, which is usually more than one http service (Server), and also includes data nodes therein, such as big data component kafka needs to expose each receiving node (spoke) address and big data component Hbase needs to expose each computing node (Region Server) address. Thus, the port number of each external service node is required to be fixed so as to meet the requirement of an original port of the big data component; however, the port number of each external service node in the container cluster is random, and the open source component does not support the mode of random port number, so that the code of the open source component needs to be changed, and the cost is high; secondly, when the application services such as the cloud host, the physical machine, and the bare metal server deployed outside the container cluster access the big data component in the container cluster, in order to ensure certain access performance and efficiency, it is also required that, compared with the application services in the container cluster, the application services outside the container cluster do not have excessive performance loss when accessing the big data component.

According to the above difficulties, even though the address of each computing node is provided by means of ingress or "node + port", the application service outside the container cluster cannot access the big data component inside the container cluster because the port number cannot be fixed. In the related art, the big data component is generally registered through a Zookeeper service, and when an application service outside the container cluster accesses the big data component in the container cluster, if an IP (Internet Protocol, IP for short) address is returned, the IP address is also only an IP address inside the container cluster, so the application service outside the container cluster still cannot access the big data component in the container cluster. Another way is to enable an application service outside the container cluster to access the big data component in the container cluster by means of static routing, which requires that the address of the pod in the container cluster is not changed, and because the pod is fixed on the node, this way does not conform to the property of automatic migration of the pod in the container cluster, so the stability of accessing the big data component in the container cluster by means of static routing is poor.

Based on the above problems, embodiments of the present invention provide a container cluster system, and a method, an apparatus, and a server for accessing a big data component, which can be applied to containerization deployment of big data components in internet technologies or other network services.

First, an embodiment of the present invention provides a container cluster System, and as shown in fig. 2, the System includes a container cluster 210 and a Domain Name System DNS (Domain Name System) service 220 outside the cluster, a big data component 230 is deployed in the container cluster, and a Domain Name of each node in the big data component 230 and a load balancer LB address corresponding to each node are recorded in the Domain Name System DNS service 220 outside the cluster.

Clustered external domain name system DNS service 220 is used to: analyzing the received first domain name to be accessed to obtain an LB address corresponding to the first domain name to be accessed, and returning the LB address corresponding to the first domain name to be accessed to the application service corresponding to the first domain name to be accessed, so that the application service accesses the node corresponding to the first domain name to be accessed in the big data assembly through the LB address corresponding to the first domain name to be accessed.

The container cluster may be a kubernets (k 8s for short) container cluster, and the container cluster may be used to run a Docker application. Before creating a Docker application, a container cluster needs to be created first, and a big data component can be deployed inside the container cluster. The big data component comprises a plurality of components with different functions, and mainly comprises systems and functions of a file system, data storage, data collection, a message system, data processing, a query engine, an analysis and report tool, scheduling and management services and the like. Generally, the application service needs to perform data collection, data storage, data analysis and other services at runtime, which requires the application service to access the corresponding big data component.

The above-mentioned out-of-cluster DNS service may run on a server outside the cluster, which may be a Bind-DNS server, and the Bind-DNS server may directly install a Bind service program to the DNS server, and the out-of-cluster DNS service may record a domain name and an LB address of each node in a big data component deployed in one or more container clusters, where the domain name may also be referred to as a domain, and is a name of a certain computer or a group of computers on the internet, which may be composed of a string of names separated by dots, and is used for identifying a computer (sometimes referred to as a geographic location) during data transmission. The LB address may be an address of a load balancer connected to a node in the container cluster; generally, one load balancer may correspond to one node, or may correspond to a plurality of nodes; when the load balancer corresponds to a plurality of nodes, LB addresses corresponding to the nodes are the same, and based on the same LB addresses, the nodes are distinguished according to domain names of the nodes. When an application service needs to access a certain node in the big data component, the application service sends a domain name to be accessed, namely the first access domain name, to the out-of-cluster DNS service.

The application service may be an application service in a different container cluster, or an application service outside the container cluster. When receiving the first domain name to be accessed, the out-of-cluster DNS service may resolve the first domain name to be accessed, find the LB address corresponding to the first domain name to be accessed, and return the obtained LB address corresponding to the first domain name to be accessed to the application service corresponding to the first domain name to be accessed, so that the application service may obtain an LB address capable of accessing a node corresponding to the first domain name to be accessed in the big data component, and the application service may access the node corresponding to the first domain name to be accessed in the big data component through the returned LB address.

The invention provides a container cluster system, which comprises a container cluster and an out-cluster DNS service; the domain name and LB address of each node in the big data assembly deployed in the container cluster are recorded in the cluster external DNS service; the domain name and the LB address of the same node are corresponding to each other; the cluster-outside DNS service is used for analyzing the received first domain name to be accessed to obtain an LB address corresponding to the first domain name to be accessed, and returning the LB address corresponding to the first domain name to be accessed to the application service corresponding to the first domain name to be accessed, so that the application service accesses the node corresponding to the first domain name to be accessed in the big data component through the LB address corresponding to the first domain name to be accessed. In the method, the out-cluster DNS service is arranged outside the container cluster, and the domain name and the LB address of each node in the big data assembly are arranged in the out-cluster DNS service, so that the application service outside the container cluster accesses the big data assembly arranged in the container cluster, and the big data assembly arranged in the container cluster can provide access service outside the container cluster.

Further, the first domain name to be accessed is sent to the out-of-cluster DNS service by the application service outside the container cluster, or the first domain name to be accessed is sent to the out-of-cluster DNS service by the container cluster.

Specifically, when an application service outside the container cluster needs to access a certain node in the big data component in the container cluster in the running process, the application service sends a first domain name to be accessed corresponding to the node to the DNS service outside the cluster, or when the application service inside the container cluster needs to access a certain node of the big data component in another container cluster in the running process, the application service sends a first domain name to be accessed corresponding to the node to the DNS service outside the cluster.

Further, as shown in fig. 3, an intra-cluster DNS service 240 is also deployed in the container cluster, and domain names and intra-cluster IP addresses corresponding to each node in the big data component are recorded in the intra-cluster DNS service 240; the domain name of the same node and the IP address in the cluster correspond to each other.

The above-described intra-cluster DNS service is used to: and analyzing a second domain name to be accessed sent by the application service in the container cluster to obtain an IP address in the cluster corresponding to the second domain name to be accessed, and returning the IP address in the cluster corresponding to the second domain name to be accessed to the application service in the container cluster, so that the application service in the container cluster accesses the node corresponding to the second domain name to be accessed in the big data assembly through the IP address in the cluster corresponding to the second domain name to be accessed.

Referring to fig. 4, the intra-cluster DNS service may be a core-DNS server, and when the server is deployed in a container cluster system with a big data component, the container cluster may automatically adopt the core-DNS to record domain names of nodes in the big data component and intra-cluster IP addresses. Where the domain name of the same node and the IP address in the cluster correspond to each other, for example, www.wikipedia.org is the domain name of a node, and the IP address corresponding to it may be 208.80.152.2. The domain name corresponding to each node of the big data assembly of the DNS service record in the cluster is the same as the domain name of each node of the big data assembly of the DNS service record outside the cluster. Com, where com corresponds to a suffix, and thus the suffix requires additional configuration, the container intra-cluster DNS service is to be configured with the suffix consistent with the suffix of the out-cluster DNS service configuration.

When an application service in the container cluster needs to access a certain node in the big data component, the application service sends a domain name to be accessed, namely the second access domain name, to the DNS service in the cluster. When receiving the second domain name to be accessed, the DNS service in the cluster can resolve the second domain name to be accessed, and since the domain name of the same node and the IP address in the cluster correspond to each other, the IP address in the cluster corresponding to the second domain name to be accessed can be obtained, and at the same time, the DNS resolver can return the IP address in the cluster corresponding to the second domain name to be accessed to the application service in the cluster corresponding to the second domain name to be accessed, so that the application service in the cluster can obtain an IP address in the cluster which can access the node corresponding to the second domain name to be accessed in the big data component, and the application service in the cluster can access the node corresponding to the second domain name to be accessed in the big data component.

For example, the first domain name to be accessed sent by the application service in the container cluster is www.ncic.ac, and the corresponding IP address is 208.80.152.2, and the DNS service in the cluster will be equivalent to an automatic telephone directory, and can directly dial the ncic name instead of the telephone number (IP address). Directly invoking the domain name, the in-cluster DNS service translates the easy-to-use name (e.g., www.ncic.ac) into an IP address (e.g., 208.80.152.2) that facilitates identification of the container cluster.

Additionally, the intra-cluster DNS service is further configured to: and if the cluster IP address corresponding to the second domain name to be accessed cannot be analyzed, sending the second domain name to be accessed to the cluster external DNS service, so that the second domain name to be accessed is analyzed through the cluster external DNS service, and an LB address corresponding to the second domain name to be accessed is obtained, so that the application service in the container cluster accesses the node corresponding to the second domain name to be accessed in the big data component through the LB address corresponding to the second domain name to be accessed.

When the application service in the cluster needs to access each node of the big data assembly in other container clusters during operation, the application service in the cluster sends a second domain name to be accessed to the DNS service in the cluster, because the DNS service in the cluster only records the domain name of each node of the big data assembly in the cluster and the IP address in the cluster, the DNS service in the cluster cannot resolve the IP address in the cluster corresponding to the second domain name to be accessed, the system can automatically send the second domain name to be accessed to the DNS service outside the cluster at the moment, the second domain name to be accessed is resolved through the DNS service outside the cluster to obtain the LB address corresponding to the second domain name to be accessed, and the application service in the LB address cluster can access the node corresponding to the second domain name to be accessed in the big data assembly. In this way, application services within a container cluster can be made to access nodes in the big data component of other container clusters through the out-of-cluster DNS service.

As shown in fig. 4, each Node of the big data component and the service are in a one-to-one correspondence relationship, the service provides a uniform service access entry and a service agent and discovery mechanism, and associates a plurality of identical PODs, which run on the Node and are a combination of a plurality of related containers (brokers). The access request is transferred to the service and then to the POD, the service is equivalent to a network tag and can also be understood as a domain name of a node running on the POD, and the application service is run in the POD.

Further, as shown in fig. 3, the above system further includes a metadata management service 250; the metadata management service 250 records the domain name of each node in the big data component; the metadata management service 250 is for: the domain names of the nodes in the big data component are provided to application services outside the container cluster or within the container cluster.

The metadata management service is a system outside the container cluster, and the recorded domain names of the nodes in the big data component are obtained after the large data component cluster container deployment is completed. The metadata management service is a way for the application services inside and outside the container cluster to obtain the domain name, and of course, the application services inside and outside the container cluster may also obtain the domain name in other manners. If the application service has already acquired the domain name corresponding to the node of a certain big data component once, the domain name corresponding to the node of the big data component is stored, and when the application service needs to access the domain name again, the application service will not acquire the domain name from the metadata management service again.

Specifically, an application server outside the container cluster can obtain a group of domain names through a metadata management service when needed, and the domain names are resolved into LB addresses accessible outside the container cluster through a DNS service outside the container cluster; the application server in the container cluster can also obtain a group of domain names through the metadata management service, and the domain names are resolved into IP addresses in the cluster through the DNS service in the container cluster, so that the addresses in the container cluster can be directly obtained, but not the addresses outside the container cluster, and the optimization of links is ensured.

Further, referring to fig. 3, a cloud management controller component 260 is also deployed within the container cluster; the cloud management controller component is to: creating LB addresses of all nodes in the big data assembly; and sending the domain name of each node in the big data assembly and the LB address of each node in the created big data assembly to the DNS service outside the cluster.

The cloud management controller component is arranged inside the container cluster, the LB addresses of all nodes in the big data component can be created by the component, and the domain names and the LB addresses of all nodes in the big data component recorded by the DNS service outside the cluster can be created and sent by the cloud management controller component inside the container cluster. The out-of-cluster DNS service may receive the domain name and LB address of each node in the big data component in a different container cluster sent by one or more in-container cluster cloud management controller components.

In addition, the cloud management controller component is further configured to: if the node of the big data assembly has a target node for changing the POD, updating an LB address corresponding to the target node according to the POD changed by the target node; and sending the updated LB address corresponding to the target node to the cluster external DNS service.

If a big data component inside the container cluster is abnormal, for example, a certain node of the big data component fails, the POD of the node needs to be changed, and the LB address corresponding to the node changes if the POD of the node changes, at this time, the cloud management controller component can automatically update the LB address corresponding to the node or switch the LB address to a normal-running POD, and finally, send the updated LB address corresponding to the node to the out-of-cluster DNS service. The stability of the service inside and outside the container cluster is ensured, and the SLA (service level agreement) of the whole container cluster is improved.

The embodiment of the invention also provides a method for accessing the big data assembly, wherein the big data assembly is deployed in the container cluster; the method is applied to a server; the server runs with cluster external DNS service; the domain name and LB address corresponding to each node in the big data assembly are recorded in the cluster external DNS service; the domain name and the LB address of the same node are corresponding to each other; the method is implemented on the basis of the system of the embodiment, as shown in fig. 5, the method includes the following steps:

step S502, receiving a domain name to be accessed of a big data assembly;

the domain name to be accessed may be a domain name corresponding to a node of a big data component deployed in a container cluster, which is sent when an application service outside the container cluster is in operation and the node needs to be accessed; or the domain name corresponding to the node is sent when the application service in the container cluster runs and needs to access the node of the big data assembly deployed in the container cluster; or the domain name corresponding to the node is sent when the application service in the container cluster runs and needs to access the node of the big data assembly deployed in other container clusters; the big data component may be a big data component deployed in a container cluster;

the domain name to be accessed is sent to DNS service outside the cluster by application service outside the container cluster; or sent by an intra-cluster DNS service in the container cluster to an extra-cluster DNS service. The domain name to be accessed of the big data receiving component can be a cluster external DNS service or a cluster internal DNS service. Specifically, when an application service outside the container cluster wants to access a certain node of the big data component in the container cluster, the application service outside the container cluster can send a domain name corresponding to the node of the big data component that wants to access to a DNS service outside the container cluster, and then the DNS service outside the container cluster receives the domain name to be accessed of the big data component; in addition, when an application service in a container cluster wants to access a certain node of a big data component in another container cluster, the application service in the container cluster can send a domain name corresponding to the node of the big data component which wants to access to a DNS service in the container cluster, and at this time, the DNS service in the cluster may not resolve the domain name to be accessed of the big data component, and then the DNS service in the cluster in the container cluster sends the domain name to a DNS service outside the cluster for resolution.

Step S504, analyzing the domain name to be accessed through the DNS service outside the cluster to obtain an LB address corresponding to the domain name to be accessed;

the domain name and the LB address of each node in the big data assembly deployed in one or more container clusters can be recorded in the cluster outside DNS service, the domain name of each node in each big data assembly has a corresponding LB address, and when the cluster outside DNS service receives the domain name to be accessed, the cluster outside DNS service can find the domain name to be accessed according to the recorded domain name of each node of the big data assembly, so that the LB address corresponding to the access domain name can be obtained.

Step S506, returning the LB address corresponding to the domain name to be accessed to the application service corresponding to the domain name to be accessed, so that the application service accesses the node corresponding to the domain name to be accessed in the big data component through the LB address corresponding to the domain name to be accessed.

After the cluster-external DNS service resolves the LB address corresponding to the domain name to be accessed, the cluster-external DNS service may return the LB address to the application service that sent the domain name to be accessed, which is equivalent to that the application service obtains the access address of the big data component that needs to be accessed, and the node corresponding to the domain name to be accessed in the big data component may be accessed through the LB address. The method further comprises the step of receiving the domain name of each node in the big data assembly and the LB address of each node in the big data assembly after creation, wherein the domain name is sent by the cloud management controller assembly in the container cluster.

The cloud management controller component is arranged inside the container cluster, the component can create LB addresses of all nodes in the big data component, and domain names and LB addresses of all nodes in the big data component recorded by the DNS service outside the cluster can be created and sent through the cloud management controller component inside the container cluster. The out-of-cluster DNS service may receive the domain name and LB address of each node in the big data component in a different container cluster sent by one or more in-container cluster cloud management controller components.

In addition, if a big data component inside the container cluster has an abnormality, for example, a node of the big data component fails, the POD of the node needs to be changed, and the change of the POD of the node causes a change of the LB address corresponding to the node, at this time, the cloud management controller component automatically updates the LB address corresponding to the node or switches the LB address to a normal-running POD, and finally sends the updated LB address corresponding to the node to the out-of-cluster DNS service. The stability of the service inside and outside the container cluster is ensured, and the SLA (service level agreement) of the whole container cluster is improved.

The invention provides a method for accessing big data components, wherein the big data components are deployed in a container cluster; the method is applied to a server; a cluster external DNS service is operated on the server; the domain name and LB address corresponding to each node in the big data assembly are recorded in the cluster external DNS service; the domain name and the LB address of the same node are corresponding to each other; the method comprises the steps that firstly, a domain name to be accessed of a big data assembly is received through a DNS service outside a cluster; then analyzing the domain name to be accessed through the DNS service outside the cluster to obtain an LB address corresponding to the domain name to be accessed; and finally, returning the LB address corresponding to the domain name to be accessed to the application service corresponding to the domain name to be accessed, so that the application service accesses the node corresponding to the domain name to be accessed in the big data assembly through the LB address corresponding to the domain name to be accessed. According to the method, the out-of-cluster DNS service is arranged outside the container cluster, and the domain name and LB address of each node in the big data assembly are arranged in the out-of-cluster DNS service, so that the application service outside the cluster accesses the big data assembly arranged in the container, and the big data assembly arranged in the container cluster can provide access service outside the container cluster. In addition, the out-of-cluster DNS service can also be used for accessing the big data assembly deployed in the container cluster by the application service in the container cluster and accessing the big data assembly deployed in the container cluster by the application service in other container clusters, so that the consistent stability of the big data assembly service in the container cluster is ensured, and the service quality of the whole container cluster system is improved.

The embodiment of the invention also provides another method for accessing the big data assembly, wherein the big data assembly is deployed in the container cluster; the method is applied to a server; the server runs an intra-cluster DNS service in a container cluster; the cluster DNS service records a domain name and a cluster IP address corresponding to each node in the big data assembly; the domain name of the same node corresponds to the IP address in the cluster; a DNS service outside the cluster is also deployed outside the container cluster; the domain name and LB address corresponding to each node in the big data assembly are recorded in the cluster external DNS service; the domain name and the LB address of the same node are corresponding to each other; the method is implemented on the basis of the system of the embodiment, as shown in fig. 6, the method includes the following steps:

step S602, analyzing a domain name to be accessed sent by an application service in a container cluster;

the cluster DNS service may record a domain name and a cluster IP address of each node of the big data component deployed in the container cluster, where the domain name is the same as the domain name of each node of the big data component recorded by the cluster DNS service, and the domain name usually does not include a suffix, so that the suffix needs to be additionally configured, and when the suffix is configured, the container cluster DNS service needs to be consistent with the suffix configured by the cluster DNS service. The application service in the container cluster can access the big data component in the container cluster and can also access the big data components in other container clusters, when the application service in the container cluster wants to access the node of the big data component in the container cluster, the application service sends the domain name to be accessed to the DNS service in the container cluster, and the DNS service in the container cluster can analyze the domain name to be accessed. When an application service in a container cluster wants to access a node of a big data component in another container cluster, the application service sends a domain name to be accessed to a DNS service in the container cluster, and the DNS service in the container cluster may not resolve the domain name to be accessed.

Step S604, if the in-cluster IP address corresponding to the domain name to be accessed is obtained through analysis, the in-cluster IP address corresponding to the domain name to be accessed is returned to the application service in the container cluster, so that the application service in the container cluster accesses the node corresponding to the domain name to be accessed in the big data assembly through the in-cluster IP address corresponding to the domain name to be accessed;

when the application service in the container cluster wants to access the node of the big data component in the container cluster, the DNS service in the container cluster can resolve to obtain the in-cluster IP address corresponding to the domain name to be accessed. Then, the DNS service in the cluster can return the IP address in the cluster to the application service corresponding to the domain name to be accessed, so that the application service can access the node corresponding to the domain name to be accessed in the big data assembly through the IP address in the cluster.

Step S606, if the cluster IP address corresponding to the domain name to be accessed cannot be analyzed, the domain name to be accessed is sent to the cluster outside DNS service, the domain name to be accessed is analyzed through the cluster outside DNS service, and the LB address corresponding to the domain name to be accessed is obtained, so that the application service in the container cluster accesses the node corresponding to the domain name to be accessed in the big data component through the LB address corresponding to the domain name to be accessed.

If the application service in the cluster wants to access each node of the big data assembly in other container clusters, because the DNS service in the cluster only records the domain name of each node of the big data assembly in the cluster and the IP address in the cluster, the DNS service in the cluster can not resolve the IP address in the cluster corresponding to the domain name to be accessed, the system can send the domain name to be accessed to the DNS service outside the cluster, the domain name to be accessed is resolved through the DNS service outside the cluster, and the LB address corresponding to the domain name to be accessed is obtained.

The invention provides another method for accessing big data components, wherein the big data components are deployed in a container cluster; the method is applied to a server; the server runs an intra-cluster DNS service in a container cluster; the cluster DNS service records a domain name and a cluster IP address corresponding to each node in the big data assembly; the domain name of the same node corresponds to the IP address in the cluster; a DNS service outside the cluster is also deployed outside the container cluster; the domain name and LB address corresponding to each node in the big data assembly are recorded in the cluster external DNS service; the domain name and the LB address of the same node are corresponding to each other; analyzing a domain name to be accessed sent by an application service in a container cluster; if the cluster IP address corresponding to the domain name to be accessed is obtained through analysis, the cluster IP address corresponding to the domain name to be accessed is returned to the application service in the container cluster, so that the application service in the container cluster accesses the node corresponding to the domain name to be accessed in the big data assembly through the cluster IP address corresponding to the domain name to be accessed; and if the cluster IP address corresponding to the domain name to be accessed cannot be analyzed, the domain name to be accessed is sent to the cluster external DNS service, so that the domain name to be accessed is analyzed through the cluster external DNS service, and the LB address corresponding to the domain name to be accessed is obtained, so that the application service in the container cluster accesses the node corresponding to the domain name to be accessed in the big data component through the LB address corresponding to the domain name to be accessed. In the method, the cluster internal DNS service and the cluster external DNS service are respectively arranged in the container cluster and outside the container cluster, so that the application service outside the container cluster accesses the big data assembly deployed in the container cluster, and the big data assembly deployed in the container cluster can provide access service outside the container cluster.

The embodiment of the invention also provides a device for accessing the big data assembly, wherein the big data assembly is deployed in the container cluster; the device is arranged on a server; the server runs with cluster external DNS service; the domain name and LB address corresponding to each node in the big data assembly are recorded in the cluster external DNS service; the domain name and the LB address of the same node are corresponding to each other; as shown in fig. 7, the apparatus includes:

a domain name receiving module 71 to be accessed, configured to receive a domain name to be accessed of the big data component;

the LB address obtaining module 72 is configured to analyze the domain name to be accessed through the DNS service outside the cluster to obtain an LB address corresponding to the domain name to be accessed;

the LB address returning module 73 is configured to return the LB address corresponding to the domain name to be accessed to the application service corresponding to the domain name to be accessed, so that the application service accesses the node corresponding to the domain name to be accessed in the big data component through the LB address corresponding to the domain name to be accessed.

Further, the domain name to be accessed is sent to a DNS service module outside the cluster by an application service outside the container cluster; or the domain name to be accessed is sent to the cluster outside DNS service module by the cluster inside DNS service in the container cluster module.

Further, the device is further configured to receive a domain name of each node in the big data component and an LB address of each node in the created big data component, where the domain name is sent by the cloud management controller component in the container cluster module.

The invention provides a device for accessing big data components, wherein the big data components are deployed in a container cluster; the device is arranged on a server; the server runs with cluster external DNS service; the domain name and LB address corresponding to each node in the big data assembly are recorded in the cluster external DNS service; the domain name and the LB address of the same node are corresponding to each other; the method comprises the steps that firstly, a domain name to be accessed of a big data assembly is received through a DNS service outside a cluster; then analyzing the domain name to be accessed through the DNS service outside the cluster to obtain an LB address corresponding to the domain name to be accessed; and finally, returning the LB address corresponding to the domain name to be accessed to the application service corresponding to the domain name to be accessed, so that the application service accesses the node corresponding to the domain name to be accessed in the big data assembly through the LB address corresponding to the domain name to be accessed. In the device, the out-of-cluster DNS service is arranged outside the container cluster, and the domain name and the LB address of each node in the big data assembly are arranged in the out-of-cluster DNS service, so that the application service outside the cluster accesses the big data assembly arranged in the container, and the big data assembly arranged in the container cluster can provide access service outside the container cluster. In addition, the out-of-cluster DNS service can also be used for accessing the big data assembly deployed in the container cluster by the application service in the container cluster and accessing the big data assembly deployed in the container cluster by the application service in other container clusters, so that the consistent stability of the big data assembly service in the container cluster is ensured, and the service quality of the whole container cluster system is improved.

The embodiment of the invention provides another device for accessing big data components, wherein the big data components are deployed in a container cluster; the device is arranged on a server; the server runs an intra-cluster DNS service in the container cluster; the cluster DNS service records a domain name and a cluster IP address corresponding to each node in the big data assembly; the domain name of the same node corresponds to the IP address in the cluster; a DNS service outside the cluster is also deployed outside the container cluster; the domain name and LB address corresponding to each node in the big data assembly are recorded in the cluster external DNS service; the domain name and the LB address of the same node are corresponding to each other; as shown in fig. 8, the apparatus includes:

a domain name resolution module 81 to be accessed, configured to resolve a domain name to be accessed sent by an application service in the container cluster;

the in-cluster IP address returning module 82 is configured to, if the in-cluster IP address corresponding to the domain name to be accessed is obtained through resolution, return the in-cluster IP address corresponding to the domain name to be accessed to the application service in the container cluster, so that the application service in the container cluster accesses the node corresponding to the domain name to be accessed in the big data component through the in-cluster IP address corresponding to the domain name to be accessed;

and the domain name sending module 83 to be visited is configured to send the domain name to be visited to the out-of-cluster DNS service if the in-cluster IP address corresponding to the domain name to be visited is not resolved, so that the domain name to be visited is resolved by the out-of-cluster DNS service, and the LB address corresponding to the domain name to be visited is obtained, so that the application service in the container cluster accesses the node corresponding to the domain name to be visited in the big data component through the LB address corresponding to the domain name to be visited.

The invention provides another device for accessing big data components, wherein the big data components are deployed in a container cluster; the device is arranged on a server; the server runs an intra-cluster DNS service in a container cluster; the cluster DNS service records a domain name and a cluster IP address corresponding to each node in the big data assembly; the domain name of the same node corresponds to the IP address in the cluster; a DNS service outside the cluster is also deployed outside the container cluster; the domain name and LB address corresponding to each node in the big data assembly are recorded in the cluster external DNS service; the domain name and the LB address of the same node are corresponding to each other; the device comprises a domain name resolution module to be accessed, a domain name resolution module and a domain name resolution module, wherein the domain name resolution module is used for resolving a domain name to be accessed, which is sent by an application service in a container cluster; the application service returns the in-cluster IP address corresponding to the domain name to be accessed to the application service in the container cluster through the in-cluster IP address access module if the in-cluster IP address corresponding to the domain name to be accessed is obtained through resolution, so that the application service in the container cluster accesses the node corresponding to the domain name to be accessed in the big data component through the in-cluster IP address corresponding to the domain name to be accessed; and if the application service cannot resolve the in-cluster IP address corresponding to the domain name to be accessed through the LB address access module, the domain name to be accessed is sent to the out-of-cluster DNS service, so that the domain name to be accessed is resolved through the out-of-cluster DNS service, and the LB address corresponding to the domain name to be accessed is obtained, so that the application service in the container cluster accesses the node corresponding to the domain name to be accessed in the big data component through the LB address corresponding to the domain name to be accessed. In the device, the in-cluster DNS service and the out-cluster DNS service are arranged in the container cluster and outside the container cluster, so that the application service outside the container cluster accesses the big data assembly deployed in the container cluster, and the big data assembly deployed in the container cluster can provide access service outside the container cluster. In addition, the out-of-cluster DNS service can also be used for accessing the big data assembly deployed in the container cluster by the application service in the container cluster and accessing the big data assembly deployed in the container cluster by the application service in other container clusters, so that the consistent stability of the big data assembly service in the container cluster is ensured, and the service quality of the whole container cluster system is improved.

An embodiment of the present invention further provides a server, as shown in fig. 9, which includes a processor and a memory, where the memory stores machine executable instructions capable of being executed by the processor, and the processor executes the machine executable instructions to implement the container cluster system of the big data component and the method for accessing the big data component.

Further, the server shown in fig. 9 further includes a bus 132 and a communication interface 133, and the processor 130, the communication interface 133 and the memory 131 are connected through the bus 132.

The Memory 131 may include a high-speed Random Access Memory (RAM) and may also include a non-volatile Memory (non-volatile Memory), such as at least one disk Memory. The communication connection between the network element of the system and at least one other network element is realized through at least one communication interface 133 (which may be wired or wireless), and the internet, a wide area network, a local network, a metropolitan area network, and the like can be used. The bus 132 may be an ISA bus, PCI bus, EISA bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one double-headed arrow is shown in FIG. 9, but this does not indicate only one bus or one type of bus.

The processor 130 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware or instructions in the form of software in the processor 130. The Processor 130 may be a general-purpose Processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; the device can also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA) or other Programmable logic device, a discrete Gate or transistor logic device, or a discrete hardware component. The various methods, steps and logic blocks disclosed in the embodiments of the present invention may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present invention may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in the memory 131, and the processor 130 reads the information in the memory 131 and completes the steps of the method of the foregoing embodiment in combination with the hardware thereof.

Embodiments of the present invention further provide a machine-readable storage medium, where the machine-readable storage medium stores machine-executable instructions, and when the machine-executable instructions are called and executed by a processor, the machine-executable instructions cause the processor to implement the container cluster system and the method for accessing a big data component, where specific implementation may refer to method embodiments, and details are not described herein.

The container cluster system, the method and the apparatus for accessing a big data component, and the computer program product of the server provided in the embodiments of the present invention include a computer-readable storage medium storing a program code, where instructions included in the program code may be used to execute the method described in the foregoing method embodiments, and specific implementations may refer to the method embodiments and are not described herein again.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.

Finally, it should be noted that: the above-mentioned embodiments are only specific embodiments of the present invention, which are used for illustrating the technical solutions of the present invention and not for limiting the same, and the protection scope of the present invention is not limited thereto, although the present invention is described in detail with reference to the foregoing embodiments, those skilled in the art should understand that: any person skilled in the art can modify or easily conceive the technical solutions described in the foregoing embodiments or equivalent substitutes for some technical features within the technical scope of the present disclosure; such modifications, changes or substitutions do not depart from the spirit and scope of the embodiments of the present invention, and they should be construed as being included therein. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

1. A container cluster system, characterized in that the system comprises a container cluster and an off-cluster domain name system, DNS, service;

a big data component is deployed in the container cluster; the domain name of each node in the big data assembly and the load balancer LB address corresponding to each node are recorded in the cluster external DNS service;

the out-of-cluster DNS service is to: analyzing the received first domain name to be accessed to obtain an LB address corresponding to the first domain name to be accessed, and returning the LB address corresponding to the first domain name to the application service corresponding to the first domain name to be accessed, so that the application service accesses the node corresponding to the first domain name to be accessed in the big data assembly through the LB address corresponding to the first domain name to be accessed.

2. The system of claim 1, wherein the first domain name to be accessed is sent by an application service outside the container cluster to the out-of-cluster DNS service; or, the first domain name to be accessed is sent to the out-of-cluster DNS service by the container cluster.

3. The system of claim 1, wherein an intra-cluster DNS service is also deployed within the container cluster; the cluster DNS service records domain names and cluster IP addresses corresponding to all nodes in the big data assembly; the domain name of the same node corresponds to the IP address in the cluster;

the intra-cluster DNS service is to: analyzing a second domain name to be accessed sent by the application service in the container cluster to obtain an IP address in the cluster corresponding to the second domain name to be accessed, and returning the IP address in the cluster corresponding to the second domain name to be accessed to the application service in the container cluster, so that the application service in the container cluster accesses a node corresponding to the second domain name to be accessed in the big data assembly through the IP address in the cluster corresponding to the second domain name to be accessed.

4. The system of claim 3, wherein the intra-cluster DNS service is further configured to:

and if the in-cluster IP address corresponding to the second domain name to be accessed cannot be analyzed, sending the second domain name to be accessed to the out-cluster DNS service, so that the second domain name to be accessed is analyzed through the out-cluster DNS service, and an LB address corresponding to the second domain name to be accessed is obtained, so that the application service in the container cluster accesses the node corresponding to the second domain name to be accessed in the big data component through the LB address corresponding to the second domain name to be accessed.

5. The system of claim 1, further comprising a metadata management service; the metadata management service records the domain name of each node in the big data assembly;

the metadata management service is to: providing the domain name of each node in the big data component to an application service outside the container cluster or an application service within the container cluster.

6. The system of claim 1, wherein a cloud management controller component is further deployed within the container cluster;

the cloud management controller component is to: creating LB addresses of all nodes in the big data assembly; and sending the domain name of each node in the big data assembly and the created LB address of each node in the big data assembly to the out-of-cluster DNS service.

7. The system of claim 6, wherein the cloud management controller component is further configured to:

if a target node for changing POD exists in each node of the big data assembly, updating an LB address corresponding to the target node according to the POD changed by the target node; and sending the updated LB address corresponding to the target node to the out-of-cluster DNS service.

8. A method of accessing a big data component, wherein the big data component is deployed in a container cluster; the method is applied to a server; the server runs an out-of-cluster DNS service; the domain name and LB address corresponding to each node in the big data assembly are recorded in the cluster external DNS service; the domain name and the LB address of the same node are corresponding to each other;

the method comprises the following steps:

receiving a domain name to be accessed of the big data component;

analyzing the domain name to be accessed through the DNS service outside the cluster to obtain an LB address corresponding to the domain name to be accessed;

and returning the LB address corresponding to the domain name to be accessed to the application service corresponding to the domain name to be accessed, so that the application service accesses the node corresponding to the domain name to be accessed in the big data assembly through the LB address corresponding to the domain name to be accessed.

9. The method of claim 8, wherein the domain name to be accessed is sent by an application service outside the container cluster to the out-of-cluster DNS service; or, the domain name to be accessed is sent to the out-of-cluster DNS service by the in-cluster DNS service in the container cluster.

10. The method of claim 8, further comprising: receiving the domain name of each node in the big data assembly and the created LB address of each node in the big data assembly, wherein the domain name is sent by the cloud management controller assembly in the container cluster.

11. A method of accessing a big data component, wherein the big data component is deployed in a container cluster; the method is applied to a server; the server runs an intra-cluster DNS service in the container cluster; the cluster DNS service records domain names and cluster IP addresses corresponding to all nodes in the big data assembly; the domain name of the same node corresponds to the IP address in the cluster; a cluster external DNS service is deployed outside the container cluster; the domain name and LB address corresponding to each node in the big data assembly are recorded in the cluster external DNS service; the domain name and the LB address of the same node are corresponding to each other;

the method comprises the following steps:

analyzing a domain name to be accessed sent by an application service in the container cluster;

if the in-cluster IP address corresponding to the domain name to be accessed is obtained through analysis, the in-cluster IP address corresponding to the domain name to be accessed is returned to the application service in the container cluster, so that the application service in the container cluster accesses the node corresponding to the domain name to be accessed in the big data assembly through the in-cluster IP address corresponding to the domain name to be accessed;

and if the cluster IP address corresponding to the domain name to be accessed cannot be analyzed, sending the domain name to be accessed to a cluster external DNS service, so that the domain name to be accessed is analyzed through the cluster external DNS service, and an LB address corresponding to the domain name to be accessed is obtained, so that the application service in the container cluster accesses the node corresponding to the domain name to be accessed in the big data component through the LB address corresponding to the domain name to be accessed.

12. An apparatus for accessing big data components, wherein the big data components are deployed in a container cluster; the device is arranged on the server; the server runs an out-of-cluster DNS service; the cluster outside DNS service module records domain names and LB addresses corresponding to each node in the big data assembly; the domain name and the LB address of the same node are corresponding to each other;

the device comprises:

the domain name receiving module to be accessed is used for receiving the domain name to be accessed of the big data assembly;

the LB address acquisition module is used for analyzing the domain name to be accessed through the DNS service outside the cluster to obtain an LB address corresponding to the domain name to be accessed;

and the LB address returning module is used for returning the LB address corresponding to the domain name to be accessed to the application service corresponding to the domain name to be accessed, so that the application service accesses the node corresponding to the domain name to be accessed in the big data assembly through the LB address corresponding to the domain name to be accessed.

13. An apparatus for accessing big data components, wherein the big data components are deployed in a container cluster; the device is arranged on the server; the server runs an intra-cluster DNS service in the container cluster; the cluster DNS service records domain names and cluster IP addresses corresponding to all nodes in the big data assembly; the domain name of the same node corresponds to the IP address in the cluster; a cluster external DNS service is deployed outside the container cluster; the domain name and LB address corresponding to each node in the big data assembly are recorded in the cluster external DNS service; the domain name and the LB address of the same node are corresponding to each other;

the device comprises:

the domain name resolution module to be accessed is used for resolving the domain name to be accessed sent by the application service in the container cluster;

the in-cluster IP address returning module is used for returning the in-cluster IP address corresponding to the domain name to be accessed to the application service in the container cluster if the in-cluster IP address corresponding to the domain name to be accessed is obtained through resolution, so that the application service in the container cluster accesses the node corresponding to the domain name to be accessed in the big data component through the in-cluster IP address corresponding to the domain name to be accessed;

and the domain name sending module to be visited is used for sending the domain name to be visited to the out-of-cluster DNS service if the in-cluster IP address corresponding to the domain name to be visited cannot be resolved, so that the domain name to be visited is resolved by the out-of-cluster DNS service, and the LB address corresponding to the domain name to be visited is obtained, so that the application service in the container cluster accesses the node corresponding to the domain name to be visited in the big data component through the LB address corresponding to the domain name to be visited.

14. A server comprising a processor and a memory, the memory storing machine executable instructions executable by the processor, the processor executing the machine executable instructions to implement the method of accessing a big data component of any of claims 8-11.

15. A machine-readable storage medium having stored thereon machine-executable instructions which, when invoked and executed by a processor, cause the processor to implement the method of accessing a big data component of any of claims 8-11.