Cross-cluster service access method, and apparatus

By receiving tenant configuration information on the cloud management platform, creating cluster groups and gateways, automatic service access between K8s clusters is solved, and the problem of high service access complexity and management cost in K8s multi-cluster environment is reduced. Resource occupancy and management complexity.

WO2024234764A1PCT designated stage expired Publication Date: 2024-11-21HUAWEI CLOUD COMPUTING TECHNOLOGIES CO LTD

Patent Information

Application Number
PCT/CN2024/077764
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-10-12
Filing Date
2024-02-20
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

K8s lacks automation solutions in multi-cluster environments, resulting in complex service access and high management costs. The existing cross-cluster access method relies on sidecar resources to occupy a large amount and manage complexity.

Method used

Provide a cross-cluster service access method, receive tenant configuration information through the cloud management platform, create cluster groups and gateways, realize the mapping relationship between service name and access address, and directly forward client requests to the target cluster to avoid sidecars.

Benefits of technology

It realizes automatic access to services in multiple clusters, which is easy to manage, reduces management costs, improves user experience, and avoids sidecar resource occupation and management complexity.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2024077764_21112024_PF_FP_ABST
    Figure CN2024077764_21112024_PF_FP_ABST
Patent Text Reader

Abstract

Provided in the present application are a cross-cluster service access method and a computing apparatus. A created cluster group is configured by a tenant, wherein a gateway may send third configuration information to each application gateway, such that after receiving a service access request of a client in a first cluster, a first application gateway can directly forward, on the basis of the obtained third configuration information, the service access request to an application gateway corresponding to another cluster, and thus it is guaranteed that the tenant can access a service in the other cluster, and automatic access between services in a plurality of clusters is realized, thereby facilitating management and saving on management costs.
Need to check novelty before this filing date? Find Prior Art

Description

A method and device for cross-cluster service access

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on May 12, 2023, with application number 202310539823.0 and invention name “A method and device for automatic discovery of cross-container cluster services and automatic network interconnection”, the entire contents of which are incorporated by reference into this application.

[0002] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on October 12, 2023, with application number 202311324854.0 and invention name “A method and device for cross-cluster service access”, the entire contents of which are incorporated by reference into this application. Technical Field

[0003] The present application relates to the field of container application technology, and more specifically, to a method and apparatus for cross-cluster service access. Background Art

[0004] Kubernetes is a lightweight and scalable open source platform for managing containerized applications and services. Kubernetes enables automated application deployment and scaling, combining application containers into a logical unit for easier management and discovery. Kubernetes effectively addresses the challenge of access between services (or applications) within a single cluster. However, it lacks an automated solution for access between services within multiple clusters, requiring only manual configuration. This complexity makes management inconvenient and error-prone. While open source service mesh projects can support cross-Kubernetes cluster access, they do so through a sidecar approach. A sidecar container is deployed in each pod, which forwards requests between services in different clusters to the sidecar container via a proxy. Service governance is performed within the sidecar container, but this consumes significant resources and carries high management costs.

[0005] Therefore, a cross-cluster service access method is needed to achieve automatic access between services in multiple clusters, thereby facilitating management and saving management costs.

[0006] Summary of the Invention

[0007] This application provides a method for cross-cluster service access, which can realize automatic access between services in multiple clusters, thereby facilitating management and saving management costs.

[0008] In the first aspect, a communication method is provided, which can be applied in a cloud service system. The method can be executed by a cloud management platform (or a device in a cloud management platform), or can be executed by a component (such as a chip or circuit) of the cloud management platform (or a device in a cloud management platform).

[0009] In this application, the cloud service system includes multiple clusters, each cluster includes at least a client and at least one working node, each working node includes at least one pod, and each pod is used to provide services.

[0010] The method includes: receiving first configuration information from a tenant, the first configuration information being used to indicate creation of a cluster group for multiple clusters; creating a cluster group based on the first configuration information, wherein the cluster group includes multiple clusters; receiving second configuration information from the tenant, the second configuration information being used to indicate creation of a gateway in the cluster group; creating a gateway in the cluster group based on the second configuration information; receiving third configuration information from the tenant, the third configuration information including: a first mapping relationship between a service name corresponding to a service included in each cluster and a corresponding access address, a second mapping relationship between a service name corresponding to a service included in each cluster and corresponding cluster information, and a third mapping relationship between each cluster and an application gateway, wherein the cluster information, the gateway is used to send the third configuration information to the application gateway corresponding to each cluster, and the application gateway is used to access the service based on a request message from the client and the third configuration information.

[0011] In this application, the access address corresponding to the service includes one or more of the following: the domain name corresponding to the service, the uniform resource locator URL corresponding to the service, and the Internet Protocol IP address corresponding to the service.

[0012] The “cluster” in this application may be, for example, a K8s cluster.

[0013] In this application, for example, "cluster information" may include: the name of the cluster, the name of the working node in the cluster, and the name of the pod in the working node.

[0014] Based on the above technical solution, the present application provides a method and computing device for cross-cluster service access. The tenant configures the created cluster group, and the gateway can send the third configuration information to each application gateway, so that when the first application gateway receives a service access request from a client in the first cluster, it can directly forward the service access request to the application gateway corresponding to the other cluster based on the obtained third configuration information, thereby ensuring that the tenant can access services in other clusters. In the present application, automatic mutual access between services of different clusters can be achieved through the configuration of the tenant in the cluster, that is, the automatic connection of the network across clusters is achieved, which is more convenient than the method of static manual configuration of the network by the tenant, improves the user's business experience, and avoids the use of sidecar to achieve cross-cluster service access, which is easy to manage and saves management costs.

[0015] In one possible implementation, multiple clusters include a first cluster and a second cluster, the first cluster includes a first client, and the first cluster is associated with a first application gateway. The method also includes: the first client obtains a first IP address corresponding to a first domain name; the first client sends a first request message to the first application gateway, the first request message carries a first IP address, and the first request message is used to request access to the first IP address; the first application gateway determines that the service identifier corresponding to the first IP address is the first identifier based on the first request message and the first mapping relationship, determines that the first identifier is the identifier corresponding to the service in the second cluster based on the second mapping relationship, and determines that the second cluster is associated with the second application gateway based on the third mapping relationship; the first application gateway sends a first request message to the second application gateway.

[0016] In a possible implementation, the gateway sends third configuration information to the first application gateway and the second application gateway.

[0017] For example, the gateway may send the third configuration information to the application gateway corresponding to each cluster based on the triggering of a service access request message from a client in a cluster in the cluster group.

[0018] Exemplarily, the gateway may send all the third configuration information to the application gateway corresponding to each cluster.

[0019] Exemplarily, the gateway may determine the configuration information that needs to be distributed based on the client's service access request message, as well as the application gateways to which the required configuration information needs to be distributed. For example, if the gateway determines based on the client's service access request message that the service access request is a request from a client in cluster #1 to access service #C in cluster #2, the gateway may only send configuration information #1 related to service #C to application gateway #1 corresponding to cluster #1 and application gateway #2 corresponding to cluster #2, where configuration information #1 is part of the configuration information in the third configuration information.

[0020] In one possible implementation, the method also includes: the second application gateway determines that the service identifier corresponding to the first IP address is the first identifier based on the first IP address and the first mapping relationship carried in the first request message, and determines that the first identifier corresponds to the second pod in the second working node in the second cluster based on the second mapping relationship; the second application gateway sends a second request message to the second pod, and the second request message is used to request access to the service corresponding to the first identifier.

[0021] In one possible implementation, the first cluster also includes a first module, and the first module is configured with a fourth mapping relationship between the domain name and the IP address. The first module is used for domain name resolution, and the first client obtains the first IP address corresponding to the first domain name, including: the first client sends a third request message to the first module, the third request message carries the first domain name, and the third request message is used to request to obtain the corresponding Internet Protocol IP address of the first domain name; the first client receives a first response message from the first module, the first response message carries the first IP address, and the first IP address is determined by the first module.

[0022] In the present application, the first module may be an extension module, for example, an operator module.

[0023] Based on the above technical solution, in this application, domain name resolution can be achieved through the first module, and service access requests can be sent to gateways corresponding to other clusters through the application gateway, thereby achieving cross-cluster service access.

[0024] In a second aspect, the present application proposes a device for executing the method of the first aspect. Specifically, the device may include units and / or modules, such as a transceiver unit and / or a processing unit, for executing a communication method proposed in the present application. In the present application, the device is applied to a cloud management platform. Alternatively, the device is a cloud management platform.

[0025] In a third aspect, the present application provides an apparatus comprising: at least one processor configured to execute a computer program or instructions stored in a memory to perform the method of the first aspect. Optionally, the apparatus further comprises a memory configured to store the computer program or instructions. Optionally, the apparatus further comprises a communication interface, through which the processor reads the computer program or instructions stored in the memory.

[0026] In one implementation, the device is a device used in a cloud management platform for implementing the functions of the above-mentioned communication method in a chip. Alternatively, the device is a cloud management platform.

[0027] In another implementation, the device is a chip, chip system or circuit used in a cloud management platform for implementing the functions of the above-mentioned communication method in a chip.

[0028] In a fourth aspect, the present application provides a processor comprising: an input circuit, an output circuit, and a processing circuit. The processing circuit is configured to receive a signal through the input circuit and transmit a signal through the output circuit, so that the processor executes the method of the first aspect.

[0029] In a specific implementation, the processor may be one or more chips, the input circuit may be an input pin, the output circuit may be an output pin, and the processing circuit may be a transistor, a gate circuit, a trigger, or various logic circuits. The input signal received by the input circuit may be, for example, but not limited to, received and input by a transceiver, and the signal output by the output circuit may be, for example, but not limited to, output to and transmitted by a transmitter. The input circuit and the output circuit may be the same circuit, which functions as an input circuit and an output circuit at different times. The embodiments of the present application do not limit the specific implementation of the processor and various circuits.

[0030] For the operations such as sending and acquiring / receiving involved in the processor, unless otherwise specified, or if they do not conflict with their actual functions or internal logic in the relevant descriptions, they can be understood as processor output, reception, input and other operations, and can also be understood as sending and receiving operations performed by the radio frequency circuit and antenna. This application does not limit this.

[0031] In a fifth aspect, a processing device is provided, comprising a processor and a memory. The processor is configured to read instructions stored in the memory and receive signals via a transceiver and transmit signals via a transmitter to execute the method of the first aspect.

[0032] Optionally, there are one or more processors and one or more memories.

[0033] Optionally, the memory may be integrated with the processor, or the memory may be provided separately from the processor.

[0034] In the specific implementation process, the memory can be a non-transitory memory, such as a read-only memory (ROM), which can be integrated with the processor on the same chip or can be set on different chips. The embodiments of the present application do not limit the type of memory and the setting method of the memory and the processor.

[0035] It should be understood that related data interaction processes, such as sending indication information, can be the process of outputting indication information from the processor, and receiving capability information can be the process of receiving input capability information from the processor. Specifically, data output by the processor can be output to the transmitter, and input data received by the processor can be received from the transceiver. The transmitter and transceiver can be collectively referred to as a transceiver.

[0036] The processing device in the fifth aspect may be one or more chips. The processor in the processing device may be implemented in hardware or software. When implemented in hardware, the processor may be a logic circuit, an integrated circuit, or the like; when implemented in software, the processor may be a general-purpose processor implemented by reading software code stored in a memory, which may be integrated into the processor or located independently of the processor.

[0037] In a sixth aspect, a computing cluster is provided, comprising at least one computing device, each computing device comprising a processor and a memory; the processor of the at least one computing device is used to execute instructions stored in the memory of the at least one computing device, so that the computing device cluster executes the method described in any possible implementation method of the first aspect.

[0038] Optionally, the processor may be a general-purpose processor, which may be implemented in hardware or software. When implemented in hardware, the processor may be a logic circuit, an integrated circuit, or the like; when implemented in software, the processor may be a general-purpose processor implemented by reading software code stored in a memory, which may be integrated into the processor or located independently of the processor.

[0039] In a seventh aspect, a computer-readable storage medium is provided, which stores a program code for execution by a device, wherein the program code includes a method for executing the above-mentioned first aspect.

[0040] In an eighth aspect, a computer program product comprising instructions is provided, which, when run on a computer, enables the computer to execute the method of the first aspect.

[0041] In a ninth aspect, a chip system is provided, comprising a processor for calling and running a computer program from a memory, so that a device equipped with the chip system executes the method of the first aspect above.

[0042] In the tenth aspect, a cloud service system is provided, which includes a cloud management platform, and computing nodes and / or network nodes, wherein the cloud management platform is used to execute the method in any possible implementation method of the above-mentioned first aspect, and the computing node is used to execute related actions of the first client, the first application gateway, and the second application gateway. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] FIG1 is a schematic diagram of the K8s cluster architecture shown in this application.

[0044] FIG2 is a schematic diagram of a cloud service scenario to which this application is applicable.

[0045] FIG3 is a schematic flowchart of a cross-cluster service access method 300 provided in this application.

[0046] FIG4 is another schematic flowchart of a cross-cluster service access method provided by the present application.

[0047] FIG5 is another schematic flowchart of a cross-cluster service access method provided by the present application.

[0048] FIG6 is another schematic diagram of a K8s cluster architecture provided in this application.

[0049] FIG7 is another schematic diagram of a K8s cluster architecture provided in this application.

[0050] FIG8 is a schematic diagram of a system architecture applicable to the present application.

[0051] FIG9 is a schematic block diagram of an apparatus 900 provided in this application.

[0052] FIG10 is a schematic block diagram of an apparatus 1000 provided in this application.

[0053] FIG11 is a schematic diagram of the architecture of a computing device cluster provided in this application.

[0054] FIG12 is a schematic diagram of a network connection between computing devices 1200A and 1200B provided by the present application. DETAILED DESCRIPTION

[0055] The technical solution in this application will be described below with reference to the accompanying drawings.

[0056] 1. K8s

[0057] K8s (Kubernetes) is an example of a well-architected distributed system that treats all machines in a cluster as part of a single resource pool. K8s has two tiers: head nodes (masters) and worker nodes (nodes). The head node, or master, consists of the control plane and the worker node applications. A K8s cluster consists of many head nodes and worker nodes.

[0058] Kubernetes is physically divided into two types of hosts: master nodes and node nodes. Master nodes are primarily responsible for scheduling and controlling cluster resources, while node nodes are primarily used to run containers and services. Master nodes store metadata, while node nodes are worker nodes primarily responsible for running various services. Node nodes regularly communicate with the master and report information through the kubelet process.

[0059] 2. pod

[0060] A pod is the smallest unit created or deployed in Kubernetes. A pod represents a running process on a cluster. A pod consists of one or more containers. Containers in a pod share network, storage, and computing resources and run on the same Docker host. A pod can run multiple containers. In production environments, a pod typically consists of a single container or multiple containers with strong dependencies. A pod can only run on a single host, while a host can have multiple pods.

[0061] 3. Container

[0062] A container is a runnable software package that contains a complete executable program, including code and runtime requirements, system libraries, and default values ​​for all important settings. Within a container, an application runs in an isolated environment, typically provided by a container engine. These containers use the host system's kernel and package the application and its dependencies together as a container. Because containers share resources with the host system, they are typically more lightweight and easier to start and stop than virtual machines.

[0063] 4. Service

[0064] In a Kubernetes cluster, each pod is assigned a unique Internet Protocol (IP) address. However, since pods have a lifecycle (they can be created and will not be restarted after being destroyed), business changes may cause this IP address to disappear at any time when the pod is destroyed.

[0065] "Services" are designed to solve this problem. A service in Kubernetes can be thought of as a gateway layer, acting as an external access interface and traffic balancer for a group of pods providing the same service. The service that clients need to access is the service object. Each service has a fixed virtual IP address that can automatically and dynamically bind to a backend pod. All network requests directly access the service's virtual IP, which is automatically forwarded to the backend. In addition to providing stable external access, services also perform load balancing, automatically distributing request traffic across all backend services. This allows for transparent horizontal scaling for customers.

[0066] Service is the core of Kubernetes, shielding service details and exposing service interfaces in a unified manner, truly achieving "microservices." For example, a service #A is deployed with three replicas, or three pods. Tenants only need to focus on the entry point of a single service, without worrying about which pod to request. This has the following advantages: First, external tenants are not aware of IP address changes caused by unexpected service crashes and Kubernetes re-spins of the pod; second, external tenants are also not aware of IP address changes caused by pod replacements due to upgrades or service changes.

[0067] Figure 1 is a schematic diagram of the internal system architecture of Kubernetes, as illustrated in this application. Two Kubernetes clusters are shown, with Kubernetes cluster #1 being used as an example. The cluster includes two working nodes, node #1 and node #2. Node #1 includes two pods, pod #11 and pod #12. Pod #11 includes two containers, one of which is container #111; pod #12 includes three containers, one of which is container #121. Node #2 in Kubernetes cluster #1 can be understood similarly, and the same can be said for Kubernetes cluster #2, which will not be further described. Currently, access between services within multiple clusters can be achieved by manually configuring gateway IP addresses and other information. This configuration is complex, inconvenient to manage, and prone to errors. In other words, the network between nodes in different clusters cannot be automatically connected and requires manual configuration. For example, the network between node #1 in Kubernetes cluster #1 and node #3 in Kubernetes cluster #2 in Figure 1 cannot be automatically connected; manual configuration of IP address information is required to enable cross-cluster service access.

[0068] In view of this, the present application provides a service access method that can realize automatic mutual access between services of different K8s clusters, realize automatic connection of networks across K8s clusters, which is more convenient than the tenant's static manual configuration of the network, improves the user's business experience, and avoids the use of sidecar to realize mutual access between services across clusters, which is convenient for management and saves management costs.

[0069] The communication method provided in the embodiment of the present application can be applied to cloud service scenarios, and the method is executed by a cloud management platform in the cloud service scenario.

[0070] FIG2 is a schematic block diagram of a cloud scenario applicable to an embodiment of the present application. As shown in FIG2 , the cloud scenario may include: a cloud management platform 210 , the Internet 220 , and a client 230 .

[0071] As shown in Figure 2, cloud management platform 210 is used to manage the infrastructure that provides multiple cloud services. This infrastructure includes multiple cloud data centers, each of which includes multiple servers. Each server includes cloud service resources to provide corresponding cloud services to tenants. In this embodiment of the present application, the cloud service resources may be cloud databases.

[0072] The cloud management platform 210 can be located in a cloud data center, which can provide an access interface (such as an interface or an application program interface (API)). The tenant can operate the client 230 to remotely access the access interface to register a cloud account and password on the cloud management platform 210, and log in to the cloud management platform 210. After the cloud management platform 210 successfully authenticates the cloud account and password, the tenant can further pay to select and purchase a virtual machine with specific specifications (processor, memory, disk) on the cloud management platform 110. After the payment is successful, the cloud management platform 210 provides the remote login account and password of the purchased virtual machine, and the client 230 can remotely log in to the virtual machine, install and run the tenant's application in the virtual machine. Therefore, the tenant can create, manage, log in and operate virtual machines in the cloud data center through the cloud management platform 210.

[0073] The functions of the cloud management platform 210 include, but are not limited to, a tenant console, computing management services, network management services, storage management services, authentication services, and image management services. The tenant console provides an interface or API for interacting with tenants. The computing management service is used to manage servers running virtual machines and containers, as well as bare metal servers. The network management service is used to manage network services (such as gateways, firewalls, etc.). The storage management service is used to manage storage services (such as data bucket services). The authentication service is used to manage tenant accounts and passwords. The image management service is used to manage virtual machine images. Tenants can use the client 210 to log in to the cloud management platform 210 via the Internet 220 to manage the rented cloud services.

[0074] In this application, the K8s cluster can be deployed in a public cloud, a private cloud, a traditional data center, or a physical machine, without limitation.

[0075] FIG3 is a schematic flow chart of a method 300 for cross-cluster service access shown in the present application. This method can be executed, for example, by the cloud management platform in the cloud service system shown in FIG2 . As previously described, the cloud service system includes multiple clusters, each of which includes at least a client and at least one worker node, each worker node includes at least one pod, and each pod is used to provide a service. As shown in FIG3 , the method includes:

[0076] 310 : Receive first configuration information from a tenant, where the first configuration information is used to instruct creation of a cluster group for multiple clusters.

[0077] The "cluster" in this application can be understood as a K8s cluster, for example.

[0078] In a possible implementation, the first configuration information includes the names of multiple clusters input by the tenant.

[0079] For example, the cloud management platform may receive first configuration information from a tenant. Assume that one cluster is named cluster #1, another cluster is named cluster #2, another cluster is named cluster #3, and so on.

[0080] 320. Create a cluster group according to the first configuration information, where the cluster group includes multiple clusters.

[0081] For example, the cloud management platform can create a "clusterset" for the tenant based on the first configuration information. The clusterset represents a cluster group. The cluster group includes each cluster deployed by the tenant. In other words, each cluster deployed by the tenant can be added to the cluster group.

[0082] 330 , receiving second configuration information from the tenant, where the second configuration information is used to instruct to create a gateway in the cluster group.

[0083] Exemplarily, the cloud management platform may receive second configuration information from the tenant.

[0084] 340. Create a gateway in the cluster group according to the second configuration information.

[0085] Exemplarily, the cloud management platform may create a gateway in the cluster group according to the second configuration information.

[0086] In this application, for example, advanced traffic management policies can be configured on the gateway.

[0087] 350. Receive third configuration information from the tenant.

[0088] In this application, the third configuration information includes: a first mapping relationship between the service name corresponding to the service included in each cluster and the access address corresponding to the service, a second mapping relationship between the service name corresponding to the service included in each cluster and the cluster information corresponding to the service, and a third mapping relationship between each cluster and the application gateway.

[0089] In this application, cluster information can be used to determine a cluster. In other words, which cluster it is can be determined based on the cluster information.

[0090] Exemplarily, the cluster information may include the name of the cluster, the name of the working node in the cluster, and the name of the pod in the working node.

[0091] In this application, for example, the access address corresponding to the service can be the domain name corresponding to the service; for another example, the access address corresponding to the service can be the uniform resource locator URL corresponding to the service; for another example, the access address corresponding to the service can be the Internet Protocol IP address corresponding to the service.

[0092] The following describes each mapping relationship included in the third configuration information.

[0093] Exemplarily, the tenant can enter the service names corresponding to the services included in each K8s cluster and their corresponding access addresses. For example, the tenant has deployed two K8s clusters, namely K8s cluster #1 and K8s cluster #2, where K8s cluster #1 includes two services, respectively denoted as service #A and service #B; K8s cluster #2 includes one service, denoted as service #C. Taking the access address as a domain name as an example, assume that the domain name of service #A is domain name #1, the domain name of service #B is domain name #2, and the domain name of service #C is domain name #3. Taking the access address as a URL as an example, assume that the URL of service #A is URL #1, the URL of service #B is URL #2, and the URL of service #C is URL #3. Taking the access address as an IP address as an example, the IP address of service #A is IP address #1, the IP address of service #B is IP address #2, and the IP address of service #C is IP address #3. For example, the first mapping relationship can be in the form of a table, as shown in Table 1 below.

[0094] Table 1

[0095] The first mapping relationship in this application can also be understood as the routing rules configured by the tenant. For example, the Hypertext Transfer Protocol (HTTP) route represents the 7-layer routing rules, the Transmission Control Protocol (TCP) route or the User Datagram Protocol (UDP) represents the 4-layer routing rules, the Transport Layer Security (TLS) represents the encryption rule routing, and the Google Remote Procedure Call Protocol (GRPC) based on HTTP2 released by Google represents the routing specifications of the GRPC protocol. The destination of the route in this application is the service imported into the cluster group.

[0096] As mentioned above, "services" are actually provided by a pod on a node in a cluster. Therefore, each service in a cluster can be located by a specific pod providing the service. For example, assume that service #A is provided by pod #11 on node #1 in K8s cluster #1; service #B is provided by pod #21 on node #2 in K8s cluster #1; and service #C is provided by pod #31 on node #3 in K8s cluster #2. For example, the second mapping relationship can be in the form of a table, as shown in Table 2 below.

[0097] Table 2

[0098] In this application, "cluster information" may include, for example, the name of the cluster, the name of the working node in the cluster, and the name of the pod in the working node. Alternatively, "cluster information" may include the name of the cluster, the address of the working node in the cluster, and the address of the pod in the working node. Alternatively, the second mapping relationship may be understood as being able to know through the second mapping relationship which pod on which node in which cluster provides a certain service. It should be noted that multiple pods can provide the same service. For example, service #A can be provided by pod #11 and pod #12 in node #1.

[0099] It should be noted that in this application, each cluster has its own corresponding application gateway, which is used to provide routing for service access requests from clients in the corresponding cluster. For example, assume that the application gateway corresponding to K8s cluster #1 is application gateway #1, the application gateway corresponding to K8s cluster #2 is application gateway #2, and the application gateway corresponding to K8s cluster #3 is application gateway #3. For example, the third mapping relationship can be in the form of a table, as shown in Table 3 below.

[0100] Table 3

[0101] It can also be understood that the address of the application gateway corresponding to each K8s cluster can be obtained according to the third mapping relationship.

[0102] 360. Configure the third configuration information to the gateway. The gateway is used to send the third configuration information to the application gateway corresponding to each cluster. The application gateway is used to access the service according to the request message of the client and the third configuration information.

[0103] For example, the gateway may send the third configuration information to the application gateway corresponding to each cluster based on the triggering of a service access request message from a client in a cluster in the cluster group.

[0104] In a possible implementation, the gateway may send all the third configuration information to the application gateway corresponding to each cluster.

[0105] In another possible implementation, the gateway may determine the configuration information to be distributed based on the client's service access request message, as well as the application gateways to which the required configuration information should be distributed. For example, if the gateway determines based on the client's service access request message that the service access request is from a client in cluster #1 requesting access to service #C in cluster #2, the gateway may only send configuration information #1 related to service #C to application gateway #1 corresponding to cluster #1 and application gateway #2 corresponding to cluster #2, where configuration information #1 is a portion of the configuration information in the third configuration information.

[0106] It should be noted that this application also configures a global controller and local controllers. The global controller is connected to the gateway and distributes third-party configuration information to each local controller when a tenant uses the cluster's services. The local controller can manage the cluster locally, with one local controller managing one or more sites. The local controller receives configuration information from the global controller and distributes it to the corresponding cluster and application gateway.

[0107] The above method 300 mainly introduces the process of tenant configuration. The above tenant configuration process can also be understood with reference to FIG4 . As shown in FIG4 , the method includes:

[0108] Step 1: Create a K8s cluster group.

[0109] For example, you can create a clusterset to represent a cluster group and add the tenant's deployed K8s cluster #1 and K8s cluster #2 to the cluster group.

[0110] Step 2: Import the services in each K8s cluster into the cluster group.

[0111] For example, you can first export the services included in each K8s cluster (service export), and then import (service import) into the cluster group. For example, you can export service #A and service #B in cluster #1 from their respective clusters, and then import them into the cluster group.

[0112] Step 3: Create a gateway in the cluster group.

[0113] Step 4: Configure the gateway.

[0114] As mentioned above, the first mapping relationship, the second mapping relationship and the third mapping relationship can be configured on the gateway. Specifically, the specific contents of the first mapping relationship to the third mapping relationship can be found in the description of step 350 of the above method 300, which will not be repeated here.

[0115] Step 5: The gateway sends configuration information to each application gateway through the global controller.

[0116] For example, when a client in a K8s cluster has a service access request, the gateway will send configuration information to the global controller, the global controller will send the configuration information to each local controller, and each local controller will send the configuration information to the corresponding application gateway.

[0117] The above method 300 introduces the tenant configuration process. The following describes how to implement cross-cluster service access based on tenant configuration.

[0118] In this application, an extension component is deployed in each K8s cluster, and the extension component is used to perform domain name resolution, wherein the fourth mapping relationship between the domain name and the IP address is configured on the extension component. For example, the extension component can be an operator.

[0119] Assume that client #1 (an example of the first client) in K8s cluster #1 needs to access service #C, then client #1 can first send a request message #1 (an example of the third request message) to the extension component, and the request message #1 carries the domain name of service #C (an example of the first domain name). The request message #1 is used to request the IP address corresponding to service #C. After receiving the request message, the extension component determines that the IP address corresponding to service #C is IP address #1 based on the configured fourth mapping relationship, and sends a response message #1 (an example of the first response message) to client #1, and the response message #1 carries the IP address #1 corresponding to service #C.

[0120] Exemplarily, after client #1 obtains the IP address corresponding to service #C, it sends a request message #2 (an example of the first request message) to application gateway #1. Request message #2 carries IP address #1. Request message #2 is used to request access to the IP address. The first application gateway determines that the identifier of the service corresponding to IP address #1 is service #C based on the received request message #2 and the configuration information #1 received from the gateway (for example, including the first mapping relationship, the second mapping relationship, and the third mapping relationship). Based on the first mapping relationship, it is determined that service #C is located in K8s cluster #2, and based on the third mapping relationship, it is determined that K8s cluster #2 is associated with application gateway #2 (an example of the first application gateway). Therefore, application gateway #1 can send request message #2 to application gateway #2. Application gateway #2 determines that the service corresponding to the IP address is service #C based on the IP address #1 carried in request message #2 and the first mapping relationship, and determines that service #C is provided by pod #7 (the second pod) on node #4 (an example of the second working node) in cluster #2 based on the second mapping relationship. Therefore, application gateway #2 sends a request message #3 (an example of a second request message) to pod #7 for requesting access to service #C.

[0121] Figure 5 shows a schematic diagram of a client accessing a service. As shown in Figure 5, the client in K8s cluster #1 sends a request message to application gateway #2 through application gateway #1, and application gateway #2 routes the request message to the corresponding pod, thereby realizing cross-cluster service access. As can be seen from Figure 5, the cross-K8s cluster service access method provided in this application can uniformly forward service access requests to the application gateway (for example, application gateway #1) corresponding to the K8s cluster, and the application gateway can do load or governance. In this application, the application gateway can provide the IP address of the pod to be accessed for providing the target service based on the received service access request, and encapsulate the service access request message (for example, using a virtual eXtensible local area network (vxlan)) and send it to the application gateway (for example, application gateway #2) corresponding to the K8s cluster where the target service is located. The application gateway only does routing and does not do load. It can also be understood that the data plane only needs to do load once, avoiding the problem of uneven load caused by multiple loads.

[0122] As can be seen from the above introduction, in this application, two new functions are extended in each tenant K8s cluster. One of the new functions is that the client's service access request can be forwarded to the application gateway corresponding to the cluster. For example, this function can be implemented by the proxy component in the K8s cluster. As shown in Figure 6, the proxy component can be the routing agent (route-agent) component in the figure. The route-agent can also monitor the services and pods of other K8s clusters and forward service access requests to the application gateway. For another example, this function can be implemented by the standard K8s cluster application program interface API. For example, as long as a K8s cluster implements this API, there is no need to deploy additional proxy components to implement this function. The definition of custom resource definitions (CRD) of the API is: "destinations" represents the list of destination network segments; "next-hop: represents the next hop information, which can be understood as the attributes included in the routing forwarding CRD. Another new feature is the implementation of automatic service discovery and automatic domain name resolution. In this application, services accessed across clusters need to be automatically injected into the tenant K8s cluster to achieve automatic access to the service. For example, this function can be implemented through an extension component, and for example, the service domain name of other sites can be resolved through a proxy component. As shown in Figure 7, the proxy component can be the domain name system (DNS) agent in Figure 7).

[0123] Exemplarily, the application gateway in this application can be a centralized gateway, for example, it can be pre-deployed. For example, it can be deployed in a virtual private cloud (VPC) on the cloud, or it can be deployed in a traditional data center, or it can be deployed in a VPC on the cloud. For example, the tenant's K8s cluster can also be deployed in a VPC, and the VPC network where the application gateway is located and the VPC network where the tenant's K8s is located are automatically connected, and the local controller connects the VPC network. For another example, the application gateway can be deployed in a traditional data center, and the tenant's K8s cluster can also be deployed in a traditional data center. The network of the application gateway and the tenant's K8s network can be pre-configured and connected through the physical network.

[0124] After the application gateway is deployed, it can be managed by the control plane. Each resource pool has a corresponding application gateway. The application gateway cluster is deployed. After the tenant K8s cluster in the resource pool joins the cluster group, it is scheduled by the control plane. For example, the mapping relationship between it and the application gateway can be configured. At this time, the cross-cluster service access requests in the tenant K8s cluster can be uniformly forwarded to the corresponding application gateway.

[0125] As described above, Figure 8 shows a schematic diagram of a system architecture applicable to the present application. As shown in Figure 8, the system architecture is divided into an orchestration layer, a global control layer, a local control layer, and a data plane forwarding layer from top to bottom. The "orchestration layer" is used to provide a service-oriented console, facilitating tenants' automatic service discovery and network interoperability across Kubernetes clusters. For example, the orchestration layer can be used to create cluster groups, manage services, manage service gateways, perform grayscale releases, manage service traffic, manage service security, manage sites, and manage gateways. The "global control layer," also known as the "global controller," is responsible for distributing tenant configurations to local controllers when tenants use services across Kubernetes clusters. For example, the global controller can be used for service discovery, cross-cluster service access, service resource management, service policy management, site resource management, and gateway resource management. The "local control layer," also known as the "local controller," manages the Kubernetes clusters within a site. A local controller can manage one or more sites. The local controller receives configurations from the global controller and distributes the configuration information to the Kubernetes cluster and application gateway. In this application, the global control layer can be separated from the local control layer. The global control layer has unified logic, while the local control layer provides local control, partial autonomy, and high reliability. The local control layer can connect to the tenant's Kubernetes control plane and the application gateway, thereby connecting to the data plane. The "data plane forwarding layer" receives configurations from the local controller and is responsible for forwarding service access requests across the Kubernetes cluster, including traffic load and other governance functions.

[0126] As mentioned above, in this application, pod is the entity that provides services. After the service access request passes through the application gateway load, it is finally forwarded to the pod. The pod can be elastically scalable. Pod changes (for example, pod location changes, or new pods are added) need to be notified to the application gateway so that the application gateway can correctly forward the service method request to the pod. The pod is managed by the tenant K8s cluster and needs to be notified by the extension component in the tenant k8s (for example, operator) in reverse to the local controller. The local controller then sends it to the local application gateway to refresh the routing information and notify the global controller. The global controller sends it to the local controllers of other clusters in the cluster group, and then the local controller notifies the application gateway to send the pod's routing information.

[0127] Based on the above solution, in this application, the tenant configures the created cluster group, and the gateway can send the third configuration information to each application gateway, so that when the first application gateway receives a service access request from a client in the first cluster, it can directly forward the service access request to the application gateway corresponding to other clusters based on the obtained third configuration information, thereby ensuring that tenants can access services in other clusters. In this application, automatic mutual access between services in different clusters can be achieved, that is, automatic connection between networks across clusters is achieved, which is more convenient than the tenant's static manual configuration of the network, improves the user's business experience, and avoids the use of sidecar to achieve service mutual access across clusters, which is easy to manage and saves management costs.

[0128] It should be understood that the term "and / or" in this document simply describes an association between related objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " in this document generally indicates that the related objects are in an "or" relationship.

[0129] Those skilled in the art should be aware that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is performed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0130] In the embodiment of the present application, the functional modules of the device can be divided according to the above method example. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical functional division. There may be other division methods in actual implementation. The following is an example of dividing each functional module according to each function.

[0131] FIG9 is a schematic block diagram of an apparatus 900 according to an embodiment of the present application. As shown in the figure, the computing apparatus 900 may include: a transceiver module 910 and a processing module 920.

[0132] Among them, the above modules are respectively used to execute the various steps of the above methods, which will not be repeated here.

[0133] It should also be understood that the apparatus 900 herein is embodied in the form of a functional unit. The term "unit" herein may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (e.g., a shared processor, a dedicated processor, or a group processor, etc.) and memory for executing one or more software or firmware programs, combined logic circuits, and / or other suitable components that support the described functionality.

[0134] The apparatus 900 of each of the above-described solutions has the function of implementing the corresponding steps of the above-described method 300. These functions can be implemented via hardware, or by hardware executing corresponding software implementations. The hardware or software includes one or more modules corresponding to the above-described functions; for example, the determination unit and the like can be replaced by a processor to respectively perform the transceiver operations and related processing operations in each method embodiment. Furthermore, the determination unit can be a processing circuit.

[0135] In a possible implementation, the device 900 may be the device in the above method 300 applied in a cloud management platform, and the device is used to execute the actions in the above method 300.

[0136] In another possible implementation, the device 900 may be the cloud management platform in the above method 300 , which is used to execute the actions in the above method 300 .

[0137] It should be noted that the device in Figure 9 can be the cloud management platform (or the device in the cloud management platform) in the aforementioned method embodiment, or it can be a chip or chip system corresponding to the cloud management platform (or the device in the cloud management platform), such as a system on chip (SoC). The processing unit is a processor, microprocessor, or integrated circuit integrated on the chip. This is not limited here.

[0138] Figure 10 is a schematic block diagram of another apparatus 1000 provided in an embodiment of the present application. As shown, apparatus 1000 includes at least one processor 1020. Processor 1020 is coupled to a memory and is configured to execute instructions stored in the memory to transmit and / or receive signals. Optionally, apparatus 1000 also includes a memory 1030 for storing instructions. Optionally, apparatus 1000 also includes a transceiver 1010, and processor 1020 controls transceiver 1010 to transmit and / or receive signals.

[0139] It should be understood that the processor 1020 and memory 1030 may be combined into a processing device, and the processor 1020 is used to execute the program code stored in the memory 1030 to implement the above functions. In specific implementations, the memory 1030 may also be integrated into the processor 1020 or independent of the processor 1020.

[0140] It should also be understood that the transceiver 1010 may include a transceiver (or receiver) and a transmitter (or transmitter). The transceiver may further include an antenna, and the number of antennas may be one or more. The transceiver 1010 may also be a communication interface or interface circuit.

[0141] Specifically, the processor 1020 in the apparatus 1000 may correspond to the processing module 920 in the apparatus 900. The transceiver 1010 in the apparatus 1000 may correspond to the processing module 910 in the apparatus 900.

[0142] As a solution, the device 1000 is used to implement the steps corresponding to the device applied in the cloud management platform in the embodiment of the above method 300.

[0143] As another solution, the device 1000 is used to implement the steps corresponding to the cloud management platform in the embodiment of the method 300 above.

[0144] For example, the processor 1020 is configured to execute computer programs or instructions stored in the memory 1030 to implement the various steps in the above method 300 .

[0145] Figure 11 is a schematic diagram of the architecture of a computing device cluster provided in an embodiment of the present application. The computing device cluster includes at least one computing device. The computing device may be a server, such as a central server, an edge server, or a local server in a local data center. In some embodiments, the computing device may also be a terminal device such as a desktop computer, a laptop computer, or a smart phone. As shown in Figure 11, the computing device cluster includes at least one computing device 1100. The memory 1030 in one or more computing devices 1100 in the computing device cluster may store the same instructions for executing the actions performed by the cloud management platform (or, the device in the cloud management platform) in the above-mentioned embodiment 300.

[0146] In some possible implementations, the memory 1130 of one or more computing devices 1100 in the computing device cluster may also store partial instructions for executing the actions performed by the cloud management platform (or a device in the cloud management platform) in the method 300 described in the above embodiment. In other words, the combination of one or more computing devices 1100 can jointly execute instructions for executing the actions performed by the cloud management platform (or a device in the cloud management platform) described in the above embodiment.

[0147] It should be noted that the memory 1130 in different computing devices 1100 in the computing device cluster may store different instructions, each for executing part of the functions of the computing device 1100. In other words, the instructions stored in the memory 1130 in different computing devices 1100 may implement the functions of one or more modules of the transceiver module 910 and the processing module 920.

[0148] Alternatively, the memory 1130 in different computing devices 1100 in the computing device cluster may store different instructions, each for executing a portion of the functions of the cloud management platform (or the devices in the cloud management platform) corresponding to the aforementioned devices 900-1000. In other words, the instructions stored in the memory 1130 in different computing devices 1100 may implement the functions of one or more modules in the transceiver module 910 and the processing module 920.

[0149] In some possible implementations, one or more computing devices in a computing device cluster may be connected via a network. The network may be a wide area network (WAN), a local area network (LAN), or the like. FIG12 illustrates one possible implementation. As shown in FIG12 , two computing devices 1200A and 1200B are connected via a network. Specifically, each computing device is connected to the network via a communication interface within the computing device.

[0150] It should be understood that the functionality of the computing device 1200A shown in FIG12 may also be implemented by multiple computing devices 1100. Similarly, the functionality of the computing device 1200B may also be implemented by multiple computing devices 1100.

[0151] This embodiment also provides a computer program product including instructions. The computer program product may be software or a program product including instructions that can be run on a computing device cluster or stored in any available medium. When executed by a computing device cluster, the computer program product causes the computing device cluster to perform the above-provided method or implement the functions of the above-provided device.

[0152] This embodiment also provides a computer-readable storage medium. The computer-readable storage medium can be any available medium capable of storing data on a computing device, or a data storage device such as a data center that includes one or more available media. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, or a magnetic tape), an optical medium (e.g., a digital video disc (DVD)), or a semiconductor medium (e.g., a solid-state drive). The computer-readable storage medium includes instructions that, when executed on a computing device, cause the computing device to perform the method provided above.

[0153] This embodiment also provides a computer-readable storage medium. The computer-readable storage medium can be any available medium capable of storing data on a computing device, or a data storage device such as a data center that includes one or more available media. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, or a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive). The computer-readable storage medium includes instructions that, when executed by a computing device cluster, cause the computing device cluster to perform the method provided above.

[0154] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

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

[0156] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0157] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of the solution of this embodiment according to actual needs.

[0158] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0159] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0160] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A method for cross-cluster service access, characterized in that: The method is applied to a cloud management platform in a cloud service system, wherein the cloud service system includes multiple clusters, each cluster includes at least a client and at least one working node, each working node includes at least one pod, and each pod is used to provide services. The method includes: receiving first configuration information from a tenant, where the first configuration information is used to instruct to create a cluster group for the plurality of clusters; Creating the cluster group according to the first configuration information, wherein the cluster group includes the multiple clusters; receiving second configuration information from the tenant, where the second configuration information is used to instruct to create a gateway in the cluster group; Creating the gateway in the cluster group according to the second configuration information; Receive third configuration information from the tenant, the third configuration information including: a first mapping relationship between a service name corresponding to a service included in each cluster and a corresponding access address, a second mapping relationship between a service name corresponding to a service included in each cluster and corresponding cluster information, and a third mapping relationship between each cluster and an application gateway corresponding to each cluster, wherein the cluster information is used to determine the cluster; The third configuration information is configured to the gateway, and the gateway is used to send the third configuration information to the application gateway corresponding to each cluster, and the application gateway is used to access the service according to the request message of the client and the third configuration information.

2. The method according to claim 1, characterized in that The access address corresponding to the service includes one or more of the following: a domain name corresponding to the service, a uniform resource locator URL corresponding to the service, and an Internet Protocol IP address corresponding to the service.

3. The method according to claim 1 or 2, characterized in that: The cluster information includes: the name of the cluster, the name of the working node in the cluster, and the name of the pod in the working node.

4. The method according to any one of claims 1 to 3, characterized in that The multiple clusters include a first cluster and a second cluster, the first cluster includes a first client, and the first cluster is associated with a first application gateway. The method further includes: The first client obtains a first IP address corresponding to the first domain name; The first client sends a first request message to the first application gateway, where the first request message carries the first IP address, and the first request message is used to request access to the first IP address; The first application gateway determines, according to the first request message and the first mapping relationship, that the service identifier corresponding to the first IP address is the first identifier, determines, according to the second mapping relationship, that the first identifier is the identifier corresponding to the service in the second cluster, and determines, according to the third mapping relationship, that the second cluster is associated with the second application gateway; The first application gateway sends the first request message to the second application gateway.

5. The method according to claim 4, characterized in that The method further comprises: The gateway sends the third configuration information to the first application gateway and the second application gateway.

6. The method according to claim 5, characterized in that: The method further comprises: The second application gateway determines, based on the first IP address and the first mapping relationship carried in the first request message, that the service identifier corresponding to the first IP address is the first identifier, and determines, based on the second mapping relationship, that the first identifier corresponds to the second pod in the second working node in the second cluster; The second application gateway sends a second request message to the second pod, where the second request message is used to request access to the service corresponding to the first identifier.

7. The method according to any one of claims 4 to 6, characterized in that The first cluster further includes a first module, on which a fourth mapping relationship between the domain name and the IP address is configured, and the first module is used for domain name resolution. The first client obtains a first IP address corresponding to the first domain name, including: The first client sends a third request message to the first module, where the third request message carries a first domain name, and the third request message is used to request to obtain an Internet Protocol IP address corresponding to the first domain name; The first client receives a first response message from the first module, where the first response message carries the first IP address, and the first IP address is determined by the first module.

8. A device, the device is applied to a cloud management platform in a cloud service system, the cloud service system includes multiple clusters, each cluster includes at least a client and at least one working node, each working node includes at least one pod, each pod is used to provide services, the device includes: Transceiver module and processing module, The transceiver module is used to receive first configuration information from a tenant, where the first configuration information is used to indicate the creation of Create a cluster group; The processing module is used to create the cluster group according to the first configuration information, wherein the cluster group includes the multiple clusters; The transceiver module is used to receive second configuration information from the tenant, where the second configuration information is used to instruct to create a gateway in the cluster group; The processing module is used for creating the gateway in the cluster group according to the second configuration information; The transceiver module is used to receive third configuration information from the tenant, the third configuration information including: a first mapping relationship between a service name corresponding to a service included in each cluster and a corresponding access address, a second mapping relationship between a service name corresponding to a service included in each cluster and corresponding cluster information, and a third mapping relationship between each cluster and an application gateway corresponding to each cluster, wherein the cluster information is used to determine the cluster; The processing module is used to configure the third configuration information to the gateway, and the gateway is used to send the third configuration information to the application gateway corresponding to each cluster, and the application gateway is used to access the service according to the request message of the client and the third configuration information.

9. The device according to claim 8, characterized in that The access address corresponding to the service includes one or more of the following: the domain name corresponding to the service, or the uniform resource locator URL corresponding to the service, or the Internet Protocol IP address corresponding to the service.

10. The device according to claim 8 or 9, characterized in that The cluster information includes: the name of the cluster, the name of the working node in the cluster, and the name of the pod in the working node.

11. The device according to any one of claims 8 to 10, characterized in that The multiple clusters include a first cluster and a second cluster, the first cluster includes a first client, and the first cluster is associated with a first application gateway, The first client is used to obtain a first IP address corresponding to the first domain name; The first client is used to send a first request message to a first application gateway, where the first request message carries the first IP address, and the first request message is used to request access to the first IP address; The first application gateway is used to determine, according to the first request message and the first mapping relationship, that the service identifier corresponding to the first IP address is the first identifier, determine, according to the second mapping relationship, that the first identifier is the identifier corresponding to the service in the second cluster, and determine, according to the third mapping relationship, that the second cluster is associated with the second application gateway; The first application gateway is used to send the first request message to the second application gateway.

12. The device according to claim 11, characterized in that The gateway is used to send the third configuration information to the first application gateway and the second application gateway.

13. The device according to claim 12, characterized in that The second application gateway is used to determine, according to the first IP address carried in the first request message and the first mapping relationship, that the service identifier corresponding to the first IP address is the first identifier, and to determine, according to the second mapping relationship, that the first identifier corresponds to the second pod in the second working node in the second cluster; The second application gateway is used to send a second request message to the second pod, where the second request message is used to request access to the service corresponding to the first identifier.

14. The device according to any one of claims 11 to 13, characterized in that The first cluster further includes a first module, on which a fourth mapping relationship between the domain name and the IP address is configured, and the first module is used for domain name resolution. The first client is used to obtain a first IP address corresponding to the first domain name, including: The first client is used to send a third request message to the first module, where the third request message carries a first domain name, and the third request message is used to request to obtain an Internet Protocol IP address corresponding to the first domain name; The first client is used to receive a first response message from the first module, where the first response message carries the first IP address, and the first IP address is determined by the first module.

15. A computing device, characterized in that: The method comprises a processor and a memory, wherein the processor runs instructions in the memory, so that the processor performs the method according to any one of claims 1 to 7.

16. A computing device cluster, characterized in that: comprising at least one computing device, each computing device comprising a processor and a memory; The processor of the at least one computing device is configured to execute instructions stored in the memory of the at least one computing device, so that the computing device cluster performs the method according to any one of claims 1 to 7.

17. A computer program product comprising instructions, characterized in that When the instructions are executed by a computing device cluster, the computing device cluster is caused to perform the method according to any one of claims 1 to 7.

18. A computer-readable storage medium, characterized in that: The method comprises computer program instructions, and when the computer program instructions are executed by a computing device cluster, the computing device cluster performs the method as claimed in any one of claims 1 to 7.

Citation Information

Patent Citations

  • Cross-cluster service access method and device

    CN118945220A

  • Business processing method and device based on application service, gateway equipment and medium

    CN110138862A

  • Cross-cluster network configuration method and device, communication equipment and storage medium

    CN113783774A

  • Service access method and device, electronic equipment and storage medium

    CN114398176A

  • Service processing method and device based on service cluster system, equipment and medium

    CN115866061A

Cited By

  • Domain name resolution method and device, storage medium and program product

    CN119814472A

  • Service request processing method, apparatus and system, device, and storage medium for cross-cluster service access

    US12634255B2