Cross‑cluster service access method, and apparatus

Abstract

This application provides a method for cross-cluster service access and a computing apparatus. A tenant configures a created cluster group, and a gateway may send third configuration information to each application gateway, so that when receiving a service access request of a client in a first cluster, a first application gateway may directly forward, based on the obtained third configuration information, the service access request to an application gateway corresponding to another cluster. In this way, it is ensured that the tenant can access a service in the another cluster, to implement automatic access between services in a plurality of clusters, thereby facilitating management and reducing management costs.

Description

(12) International application published under the Patent Cooperation Treaty (19) International Bureau of WIPO (43) International Publication Date November 21, 2024 (21.11.2024) WIPO I PCT (51) International Patent Classification: H04L 67 / 51 (2022.01) (21) International Application Number: (22) International Application Date: (25) Application Language: (26) Publication Language: (30) Priority: 202310539823.0 202311324854.0 PCT / CN2024 / 077764 February 20, 2024 (20.02.2024) Chinese Chinese May 12, 2023 (12.05.2023) CN October 12, 2023 (12.10.2023) CN (71) Applicant: Huawei Cloud Computing Technologies Co., Ltd. [CN / CN]; Huawei Cloud Data Center, Jiaoxinggong Road, Qianzhong Avenue, Gui'an New District, Guiyang City, Guizhou Province, China 550025 (CN) 0 lllllllllllllllllllllllllllllllll^ (10) International Publication No.: WO 2024 / 234764 Al (72) Inventors: Zhu Na; Huawei Cloud Data Center, Jiaoxinggong Road, Qianzhong Avenue, Gui'an New District, Guiyang City, Guizhou Province, China 550025 (CN) 0 Yao Bo; Huawei Cloud Data Center, Jiaoxinggong Road, Qianzhong Avenue, Gui'an New District, Guiyang City, Guizhou Province, China 550025 (CN) 0 Yang Yi; Huawei Cloud Data Center, Jiaoxinggong Road, Qianzhong Avenue, Gui'an New District, Guiyang City, Guizhou Province, China 550025 (CN)0 ZHANG, Caizheng; Huawei Cloud Data Center, Jiaoxinggong Road, Qianzhong Avenue, Guian New District, Guiyang City, Guizhou Province, China 550025 (CN)0 (74) Agent: LONGSUN LEAD IP LTD.; Room 801-1, 8th Floor, Building 3, Zone 2, No. 81 Beiqing Road, Haidian District, Beijing, China 100094 (CN)0 (81) Designated Country (unless otherwise specified, each of which requires available national protection): AE, AG, AL, AM, AO, AT, AU, AZ, BA, BB, BG, = -== = - = = = = = = = = = = === Method 300 Figure 3 (54) Title:CROSS-CLUSTER SERVICE ACCESS METHOD, AND APPARATUS (54)Title of the invention: A cross-cluster service access method and apparatus 300 Method 310 Receive first configuration information from a tenant, wherein the first configuration information is used for giving an instruction to create a cluster group for a plurality of clusters 320 Create the cluster group according to the first configuration information, wherein the cluster group comprises the plurality of clusters 330 Receive second configuration information from the tenant, wherein the second configuration information is used for giving an instruction to create a gateway in the cluster group 340 Create the gateway in the cluster group according to the second configuration information 350 Receive third configuration information from the tenant 360 Configure the third configuration information for the gateway, wherein the gateway is configured to send the third configuration information to an application gateway corresponding to each cluster, and the application gateway is configured toexecuting service access according to a request message of a client and the third configuration information (57) Abstract: A cross-cluster service access method and a computing device are provided in the present application. A created cluster group is configured by a tenant, wherein a gateway can send third configuration information to each application gateway, so that after receiving a service access request from a client in a first cluster, a first application gateway can directly forward the service access request to an application gateway corresponding to another cluster based on the obtained third configuration information, thereby ensuring that the tenant can access a service in the other cluster, realizing automatic access between services in a plurality of clusters, facilitating management and saving management costs. [See continuation page] WO 2024 / 234764 A1 IIIIIIIIIIIIIIIIIIIIIIIIIIIIM BH, BN, BR, BW, BY BZ, CA, CH, CL, CN, CO, CR, CU, CY CZ, DE, DJ, DK,DM, DO, DZ, EC, EE, EG, ES, FI, GB, GD, GE, GH, GM, GT, HN, HR, HU, ID, IL, IN, IQ, IR, IS, IT, JM, JO, JP, KE, KG, KH, KN, KP, KR, KW, KZ, LA, LC, LK, LR, LS, LU, LY MA, MD, MG, MK, MN, MU, MW, MX, MY MZ, NA, NG, NI, NO, NZ, OM, PA, PE, PG, PH, PL, PT, QA, RO, RS, RU, RW, SA, SC, SD, SE, SG, SK, SL, ST, SY SY TH, TJ, TM, TN, TR, TT, TZ, UA, UG, US, UZ, VC, VN, WS, ZA, ZM, ZWO (84) Designated countries (unless otherwise specified, each requiring available regional protection): ARIPO (BW, CV, GH, GM, KE, LR, LS, MW, MZ, NA, RW, SC, SD, SL, ST, SZ, TZ, UG, ZM, ZW), Eurasia (AM, AZ, BY, KG, KZ, RU, TJ, TM), Europe (AL, AT, BE, BG, CH, CY, CZ, DE, DK, EE, ES, FI, FR, GB, GR, HR, HU, IE, IS, IT, LT, LU, LV, MC, ME, MK, MT, NL, NO, PL, PT, RO, RS, SE, SI, SK, SM, TR), OAPI (BF, BJ, CF, CG, CI, CM, GA, GN, GQ, GW, KM, ML, MR, NE, SN, TD, TG). This international publication includes: an international search report (Article 21(3) of the Treaty). (57) Abstract: This application provides a method and computing device for cross-cluster service access. By configuring the created cluster group by the tenant, the gateway can send third configuration information to each application gateway. 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. This ensures that the tenant can access services in other clusters, realizes automatic access between services in multiple clusters, facilitates management, and saves management costs. WO 2024 / 234764PCT / CN2024 / 077764 A Method and Apparatus for Cross-Cluster Service Access This application claims priority to Chinese Patent Application No. 202310539823.0, filed on May 12, 2023, entitled "A Method and Apparatus for Automatic Service Discovery and Automatic Network Interoperability Across Container Clusters," the entire contents of which are incorporated herein by reference. This application also claims priority to Chinese Patent Application No. 202311324854.0, filed on October 12, 2023, entitled "A Method and Apparatus for Cross-Cluster Service Access," the entire contents of which are incorporated herein by reference. Technical Field This application relates to the field of container application technology, and more specifically, to a method and apparatus for cross-cluster service access. Background Art Kubernetes (K8s) is a lightweight and scalable open-source platform for managing containerized applications and services. Kubernetes (K8s) enables automated deployment and scaling of applications. K8s groups application containers into logical units for easier management and discovery. While K8s effectively solves the problem of access between services (or applications) within a single cluster, it lacks an automated solution for access between services across multiple clusters. Currently, access requires manual configuration, which is complex, inconvenient to manage, and prone to errors. While open-source service mesh projects support cross-K8s cluster service access, this is achieved through sidecars. Each pod deploys a sidecar container, which proxies and forwards access between services from different clusters to the sidecar container. Service governance is handled within the sidecar container, but this approach consumes significant resources and incurs high management costs. Therefore, a method for cross-cluster service access is needed to automate access between services across multiple clusters, thereby simplifying management and reducing management costs. This application provides a method for cross-cluster service access that enables automatic access between services across multiple clusters, facilitating management and reducing management costs. Firstly, a communication method is provided, which can be applied to a cloud service system. This method can be executed by a cloud management platform (or, devices within the cloud management platform), or by components (e.g., chips or circuits) of the cloud management platform (or, devices within the cloud management platform). In this application, the cloud service system includes multiple clusters, each cluster including at least a client and at least one worker node, each worker node including at least one pod, and each pod used to provide services. The method includes: receiving first configuration information from a tenant, the first configuration information indicating the creation of a cluster group for the multiple clusters; and according to...The first configuration information includes creating a cluster group, wherein the cluster group includes multiple clusters; receiving second configuration information from a tenant, the second configuration information being used to instruct the creation of a gateway in the cluster group; creating a gateway in the cluster group according to the second configuration information; receiving third configuration information from a tenant, the third configuration information including: a first mapping relationship between the service name and the corresponding access address of the service included in each cluster, a second mapping relationship between the service name and the corresponding cluster information of the service included in each cluster, and a third mapping relationship between each cluster and the application gateway, wherein the cluster information and the gateway are 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 client's request message and the third configuration information. 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. In this application, "cluster" can be, for example, a K8s cluster. In this application, "cluster information" can include: the name of the cluster, the name of the worker node in the cluster, and the name of the pod in the worker node. Based on the above technical solution, this application provides a method and computing device for cross-cluster service access. By configuring the created cluster group by the tenant, the gateway can send third configuration information to each application gateway. 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 corresponding application gateway in other clusters based on the obtained third configuration information, thereby ensuring that the tenant can access services in other clusters. In this application, by configuring the cluster within the tenant, automatic service access between different clusters can be achieved, i.e., automatic network connectivity between cross-clusters is realized. This is more convenient than the static manual network configuration method by the tenant, improves the user's business experience, and avoids the use of sidecars to achieve cross-cluster service access, facilitating management and saving management costs. In one possible implementation, multiple clusters include a first cluster and a second cluster. The first cluster includes a first client and is associated with a first application gateway. The method further includes: the first client obtaining a first IP address corresponding to a first domain name; the first client sending a first request message to the first application gateway, the first request message carrying the first IP address, the first request message being used to request access to the first IP address; the first application gateway determining, based on the first request message and a first mapping relationship, that the service identifier corresponding to the first IP address is a first identifier, determining, based on a second mapping relationship, that the first identifier is the identifier corresponding to a service in the second cluster, and determining, based on a third mapping relationship, that the second cluster is associated with the second application gateway; and the first application gateway sending the first request message to the second application gateway.In one possible implementation, the gateway sends third configuration information to both the first and second application gateways. For example, the gateway can send third configuration information to the application gateways corresponding to each cluster based on a service access request message from a client in a cluster group. Exemplarily, the gateway can send all the third configuration information to the respective application gateways of each cluster. Exemplarily, the gateway can determine the configuration information to be sent and which application gateways to send the required configuration information to based on the client's service access request message. 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, then the gateway can send configuration information #1 related to service #C only to the application gateway #1 corresponding to cluster #1 and the application gateway #2 corresponding to cluster #2, where configuration information #1 is a portion of the third configuration information. In one possible implementation, the method further includes: a second application gateway determining the service identifier corresponding to the first IP address as a first identifier based on the first IP address and the first mapping relationship carried in the first request message, and determining that the first identifier corresponds to a second pod in the second worker node of the second cluster based on the second mapping relationship; the second application gateway sending a second request message to the second pod, the second request message being used to request access to the service corresponding to the first identifier. In one possible implementation, the first cluster further includes a first module, the first module being configured with a fourth mapping relationship between domain names and IP addresses, the first module being used for domain name resolution, and the first client obtaining the first IP address corresponding to the first domain name including: the first client sending a third request message to the first module, the third request message carrying the first domain name, the third request message being used to request obtaining the Internet Protocol IP address corresponding to the first domain name; the first client receiving a first response message from the first module, the first response message carrying the first IP address, the first IP address being determined by the first module. In this application, the first module can be an extension module, for example, it can be an operator module. Based on the above technical solutions, 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 enabling cross-cluster service access. Secondly, this application proposes an apparatus for performing the method described in the first aspect. Specifically, the apparatus may include units and / or modules for performing the communication method proposed in this application, such as transceiver units and / or processing units. In this application, the apparatus is applied to a cloud management platform. Alternatively, the apparatus is a cloud management platform. Thirdly, this application provides an apparatus comprising: at least one processor for performing computer storage in memory.The device includes a program or instructions to execute the method described in the first aspect. Optionally, the device further includes a memory for storing computer programs or instructions. Optionally, the device further includes a communication interface through which the processor reads the computer programs or instructions stored in the memory. In one implementation, the device is an apparatus for implementing the communication method described above in a chip and applied in a cloud management platform. Alternatively, the device is a cloud management platform. In another implementation, the device is a chip, chip system, or circuit for implementing the communication method described above in a chip and applied in a cloud management platform. In a fourth aspect, this application provides a processor, including: an input circuit, an output circuit, and a processing circuit. The processing circuit is used to receive signals through the input circuit and transmit signals through the output circuit, causing the processor to execute the method described in the first aspect. In specific implementations, the processor can be one or more chips, the input circuit can be an input pin, the output circuit can be an output pin, and the processing circuit can be a transistor, a gate circuit, a flip-flop, and various logic circuits, etc. The input signal received by the input circuit can be received and input by, for example, but not limited to, a transceiver. The signal output by the output circuit can be output to, for example, but not limited to, a transmitter and transmitted by the transmitter. The input circuit and output circuit can be the same circuit, which is used as the input circuit and output circuit at different times. This application does not limit the specific implementation of the processor and various circuits. 2 WO 2024 / 234764 PCT / CN2024 / 077764 For the transmission and acquisition / reception operations involved in the processor, unless otherwise specified, or if it does not contradict its actual function or internal logic in the relevant description, it can be understood as the processor output and reception, input, etc., or as the transmission and reception operations performed by the radio frequency circuit and the antenna. This application does not limit this. In a fifth aspect, a processing device is provided, including a processor and a memory. The processor is used to read instructions stored in the memory and can receive signals through a transceiver and transmit signals through a transmitter to execute the method of the first aspect described above. Optionally, the processor and the memory can be one or more. Optionally, the memory can be integrated with the processor, or the memory and processor can be separately configured. In specific implementations, the memory can be a non-transitory memory, such as read-only memory (ROM), which can be integrated with the processor on the same chip or disposed on different chips. This application does not limit the type of memory or the configuration of the memory and processor. It should be understood that related data interaction processes, such as sending indication information, can be a process of outputting indication information from the processor, and receiving indication information...The information can be the process by which a processor receives input capability information. Specifically, the data output by the processor can be output to a transmitter, and the input data received by the processor can come from a transceiver. The transmitter and transceiver can be collectively referred to as a transceiver. The processing device in the fifth aspect above can be one or more chips. The processor in this processing device can be implemented in hardware or software. When implemented in hardware, the processor can be a logic circuit, integrated circuit, etc.; when implemented in software, the processor can be a general-purpose processor, implemented by reading software code stored in memory. This memory can be integrated into the processor or located outside the processor and exist independently. In a sixth aspect, a computing cluster is provided, including at least one computing device, each computing device including 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 of the first aspect. Optionally, the processor can be a general-purpose processor, implemented in hardware or software. When implemented in hardware, the processor can be a logic circuit, integrated circuit, etc.; when implemented in software, the processor can be a general-purpose processor, implemented by reading software code stored in memory. This memory can be integrated into the processor or located outside the processor and exist independently. A seventh aspect provides a computer-readable storage medium storing program code for execution by a device, the program code including methods for performing the first aspect described above. An eighth aspect provides a computer program product containing instructions, which, when run on a computer, causes the computer to perform the methods of the first aspect described above. A ninth aspect provides a chip system including a processor for calling and running a computer program from memory, causing a device equipped with the chip system to perform the methods of the first aspect described above. A tenth aspect provides a cloud service system including a cloud management platform, and computing nodes and / or network nodes, wherein the cloud management platform is used to perform the methods in any possible implementation of the first aspect described above, and the computing nodes are used to perform related actions of a first client, a first application gateway, and a second application gateway. Figure 1 is a schematic diagram of the K8s cluster architecture shown in this application. Figure 2 is a schematic diagram of a cloud service scenario to which this application applies. Figure 3 is a schematic flowchart of a cross-cluster service access method 300 provided by this application. Figure 4 is another schematic flowchart of a cross-cluster service access method provided by this application. Figure 5 is yet another schematic flowchart of a cross-cluster service access method provided by this application. Figure 6 is another schematic diagram of a K8s cluster architecture provided by this application. Figure 7 is yet another schematic diagram of a K8s cluster architecture provided by this application.Figure 8 is a schematic diagram of a system architecture applicable to this application. Figure 9 is a schematic block diagram of the device 900 provided in this application. Figure 10 is a schematic block diagram of the device 1000 provided in this application. Figure 11 is a schematic diagram of the architecture of a computing device cluster provided in this application. Figure 12 is a schematic diagram of the connection between computing devices 1200A and 1200B provided in this application via a network. 3 WO 2024 / 234764 PCT / CN2024 / 077764 Detailed Description The technical solutions in this application will be described below with reference to the accompanying drawings. 1. K8s K8s (Kubemetes) 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 layers: master nodes and worker nodes. The master node consists of a control plane and worker node applications. A K8s cluster consists of many master nodes and worker nodes. When physically partitioning, K8s divides into two types of hosts, master nodes and node nodes. In Kubernetes (K8s), the master node is primarily used for scheduling and controlling cluster resources, while the node nodes are mainly used to run containers, i.e., the nodes that run services. The master node stores various metadata, while the node nodes are worker nodes primarily used to run various services. Node nodes communicate with the master node periodically and report information through the kubelet process. 2. Pod: A pod is the smallest unit of creation or deployment in K8s. A pod represents a process running on the cluster. A pod consists of one or more containers, which share network, storage, and compute resources and run on the same Docker host. A pod can run multiple containers, but in production environments, it is typically a single container or multiple strongly related and complementary containers forming a pod. A pod can only run on one host, but a host can have multiple pods. 3. Container: A container is a runnable software package containing a complete executable program, including code and default values ​​for the application, system libraries, and all important settings required at runtime. Inside a container, the application runs in an independent environment, usually provided by a container engine. They 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. 4. Services: In a Kubernetes cluster, although each pod is assigned a separate Internet Protocol (IP) address, [the rest of the text is missing].Pods have a lifecycle (they can be created and destroyed, and will not be restarted), and their IP addresses may disappear along with the pod's destruction due to business changes. "Services" are used to solve this problem. In Kubernetes, a service can be understood as a gateway layer, a public interface for a group of pods providing the same service, and a traffic balancer. Clients access the service object, and each service has a fixed virtual IP address that can be automatically and dynamically bound to backend pods. All network requests directly access the service's virtual IP, and the service automatically forwards them to the backend. Besides providing a stable way to access the outside world, services also perform load balancing, automatically distributing request traffic to all backend services. Services can achieve horizontal scaling transparently to clients. Services are the core of Kubernetes services, shielding service details and uniformly exposing service interfaces, truly achieving "microservices." For example, a service #A might be deployed with 3 replicas, or 3 pods. For a tenant, they only need to focus on the ingress of one service, without needing to know which pod to request. The advantages of this approach are twofold: firstly, external tenants do not need to be aware of IP changes caused by unexpected service crashes on pods or Kubernetes restarting the pods; secondly, external tenants do not need to be aware of IP address changes caused by pod replacements due to service upgrades or changes. Figure 1 is a schematic diagram of an internal system architecture of Kubernetes as illustrated in this application. Figure 1 shows two Kubernetes clusters, with Kubernetes cluster #1 as an example. This cluster includes two worker nodes, node#1 and node#2. Node#1 contains two pods, pod#11 and pod#12. Pod#11 contains two containers, one of which is container #111; pod#12 contains three containers, one of which is container #121. Node#2 in Kubernetes cluster #1 can be understood similarly, and so can Kubernetes cluster #2, which will not be elaborated further. Currently, access between services within multiple clusters can be achieved by manually configuring gateway IP addresses and other information, which is complex, inconvenient to manage, and prone to errors. In other words, network connectivity between nodes in different clusters cannot be established automatically 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 established automatically; some IP address information needs to be manually configured to enable cross-cluster service access.In view of this, this application provides a service access method that enables automatic service communication between different Kubernetes clusters, achieving automatic network connectivity across Kubernetes clusters. This is more convenient than the static manual network configuration method for tenants, improving user experience and avoiding the use of sidecars for cross-cluster service communication, thus simplifying management and saving management costs. The communication method provided in this application embodiment can be applied to cloud service scenarios, and the method is executed by the cloud management platform in the cloud service scenario. The cloud service scenario will be described in detail below with reference to Figure 2. Figure 2 is a schematic block diagram of a cloud scenario applicable to an embodiment of this application. As shown in Figure 2, the cloud scenario may include: a cloud management platform 210, the Internet 220, and a client 230. As shown in Figure 2, the cloud management platform 210 is used to manage the infrastructure providing multiple cloud services. The infrastructure includes multiple cloud data centers, each containing multiple servers, and each server includes cloud service resources to provide corresponding cloud services to tenants. In this embodiment, the cloud service resources may be cloud databases. A cloud management platform 210 may be located in a cloud data center and can provide access interfaces (such as user interfaces or application program interfaces, APIs). Tenants can use client 230 to remotely access the access interface to register a cloud account and password on the cloud management platform 210 and log in. After successful authentication of the cloud account and password, the tenant can further select and purchase virtual machines of specific specifications (processor, memory, disk) on the cloud management platform 210. After successful purchase, the cloud management platform 210 provides the remote login account and password for the purchased virtual machine, and client 230 can remotely log in to the virtual machine to install and run the tenant's application. Therefore, tenants can create, manage, log in to, and operate virtual machines in the cloud data center through the cloud management platform 210. The cloud management platform 210 includes, but is not limited to, a tenant console, compute management services, network management services, storage management services, authentication services, and image management services. The tenant console provides an interface or API for interaction with tenants. The compute management services manage servers running virtual machines and containers, as well as bare metal servers. The network management services manage network services (such as gateways and firewalls). The storage management services manage storage services (such as data bucket services). The authentication services manage tenant account passwords. The image management services manage virtual machine images. Tenants use client 210 and can log in to the cloud management platform 210 via the internet 220 to manage their rented cloud services.In this application, the Kubernetes cluster can be deployed on a public cloud, a private cloud, a traditional data center, or a physical machine, without limitation. Figure 3 is a schematic flowchart of a cross-cluster service access method 300 shown in this application, which can be executed, for example, by a cloud management platform in the cloud service system shown in Figure 2. As described above, the cloud service system includes multiple clusters, each cluster including at least a client and at least one worker node, each worker node including at least one pod, and each pod providing services. As shown in Figure 3, the method includes: 310, receiving first configuration information from a tenant, the first configuration information indicating the creation of a cluster group for multiple clusters. In this application, "cluster" can be understood, for example, as a Kubernetes cluster. In one possible implementation, the first configuration information includes the names of multiple clusters input by the tenant. For example, the cloud management platform can receive the first configuration information from the tenant. Assume that the name of one cluster can be referred to as cluster #1, the name of another cluster can be referred to as cluster #2, the name of yet another cluster can be referred to as cluster #3, and so on. 320, creating a cluster group according to the first configuration information, wherein the cluster group includes multiple clusters. For example, the cloud management platform can create a "clusterset" for a tenant based on the first configuration information. This clusterset represents a cluster group. The cluster group includes the various clusters deployed by the tenant. In other words, the various clusters deployed by the tenant can be added to this cluster group. 330, Receive second configuration information from the tenant, the second configuration information being used to instruct the creation of a gateway in the cluster group. For example, the cloud management platform can receive the second configuration information from the tenant. 340, Create a gateway in the cluster group based on the second configuration information. For example, the cloud management platform can create a gateway in the cluster group based on the second configuration information. In this application, for example, advanced traffic governance policies can be configured on the gateway. 350, Receive third configuration information from the tenant. 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. In this application, the cluster information can be used to determine the cluster. In other words, the cluster information can be used to determine which cluster it is. For example, cluster information may include the name of the cluster, the names of the worker nodes in the cluster, and the names of the pods within the worker nodes. In this application, for example, the access address corresponding to a service may be the domain name corresponding to the service; another example is that the access address corresponding to a service may be the Uniform Resource Locator (URL) corresponding to the service; yet another example is that the access address corresponding to a service may be the Internet Protocol (IP) address corresponding to the service.The following describes the various mapping relationships included in the third configuration information. For example, a tenant can input the service name and corresponding access address for each service included in each Kubernetes cluster. Example 5 WO 2024 / 234764 PCT / CN2024 / 077764: For instance, a tenant deploys two Kubernetes clusters, Kubernetes cluster #1 and Kubernetes cluster #2. Kubernetes cluster #1 includes two services, denoted as service #A and service #B; Kubernetes cluster #2 includes one service, denoted as service #C. Taking access addresses as domain names, assume that the domain name for service #A is domain #1, the domain name for service #B is domain #2, and the domain name for service #C is domain #3. Taking access addresses as URLs, assume that the URL for service #A is URL #1, the URL for service #B is URL #2, and the URL for service #C is URL #3. Taking IP addresses as the access 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. Table 1 Service Name Access Address Service #A Domain #1, URL #1, IP Address #1 Service #B Domain #2, URL #2, IP Address #2 Service #C Domain #3, URL #3, IP Address #3 The first mapping relationship in this application can also be understood as the routing rules configured by the tenant. For example, Hypertext Transfer Protocol (HTTP) routing represents Layer 7 routing rules, Transmission Control Protocol (TCP) routing or User Datagram Protocol (UDP) routing represents Layer 4 routing rules, Transport Layer Security (TLS) represents encrypted routing rules, and Google's Google Remote Procedure Call Protocol (GRPC) based on HTTP / 2 represents the gRPC routing specification. In this application, the destination of the routing is the service imported into the cluster group. As mentioned earlier, a "service" is actually provided by a specific pod on a specific node in a cluster. Therefore, the service in each cluster can be located to the specific pod that provides the service. For example, suppose service #A is provided by pod #11 in node #1 of Kubernetes cluster #1; service #B is provided by pod #21 in node #2 of Kubernetes cluster #1; and service #C is provided by...The service is provided by pod #31 on node #3 in Kubernetes cluster #2. For example, the second mapping relationship can be in tabular form, as shown in Table 2 below. Table 2 Service Name Access Address Service #A Kubernetes Cluster #1—node #1—pod #11 Service #B Kubernetes Cluster #1—node #2—pod #21 Service #C Kubernetes Cluster #2—node #3—pod #31 In this application, "cluster information" may include, for example, the name of the cluster, the names of the worker nodes in the cluster, and the names of the pods on the worker nodes. Alternatively, "cluster information" may include the name of the cluster, the addresses of the worker nodes in the cluster, and the addresses of the pods on the worker nodes. Alternatively, the second mapping relationship can be understood as knowing which pod on which node in which cluster provides a particular 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 on node #1. 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 its respective 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. Table 3 Cluster Application Gateways K8s Cluster Application Gateway #1 K8s Cluster #2 Application Gateway #2 K8s Cluster #3 Application Gateway #3 This can also be understood as obtaining the address of the application gateway corresponding to each K8s cluster based on the third mapping relationship. 360. The third configuration information is configured to the gateway, which is used to send the third configuration information to the application gateway corresponding to each cluster. This application gateway is used to perform service access based on the client's request message and the third configuration information. For example, the gateway can send the third configuration information to the application gateways corresponding to each cluster based on the triggering of a service access request message from a client in a certain cluster within the cluster group. In one possible implementation, the gateway can send all the third-party configuration information to the respective application gateways of each cluster. In another possible implementation, the gateway can determine the configuration information to be sent based on the client's service access request message, and which application gateways to send the required configuration information to. For example, if the gateway determines from 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, then the gateway can only send the required configuration information to the application gateway corresponding to cluster #1.Gateway #1 and application gateway #2 corresponding to cluster #2 send configuration information #1 related to service #C, where configuration information #1 is a part of the configuration information in the third configuration information. It should be noted that this application also configures a global controller and various local controllers. The global controller is connected to the gateway. When a tenant accesses the services of the cluster, it distributes the third configuration information to each local controller. The local controller can manage the cluster locally. One local controller manages one or more sites. The local controller receives the configuration information from the global controller and distributes the configuration information to the corresponding cluster and application gateway. The above method 300 mainly introduces the tenant configuration process. The tenant configuration process can also be understood with reference to Figure 4. As shown in Figure 4, the method includes: Step 1, creating a K8s cluster group. For example, a clusterset can be created to represent a cluster group, and the K8s cluster #1 and K8s cluster #2 deployed by the tenant can be added to this cluster group. Step 2, importing the services in each K8s cluster into the cluster group. For example, services included in each Kubernetes cluster can be exported (service export) and then imported (service import) into the cluster group. For example, services #A and #B in cluster #1 can be exported from their respective clusters and then imported into the cluster group. Step 3: Create a gateway in the cluster group. Step 4: Configure the gateway. As mentioned above, a first mapping relationship, a second mapping relationship, and a third mapping relationship can be configured on the gateway. Specifically, the details of the first to third mapping relationships can be found in the description of step 350 of method 300 above, and will not be repeated here. Step 5: The gateway sends configuration information to each application gateway through the global controller. For example, when a client in a Kubernetes cluster makes a service access request, the gateway sends configuration information to the global controller, the global controller sends the configuration information to each local controller, and each local controller sends the configuration information to its corresponding application gateway. Method 300 above describes the tenant configuration process. The following describes how to achieve cross-cluster service access based on tenant configuration. In this application, an extension component is deployed in each Kubernetes cluster. This extension component is used for domain name resolution, and it is configured with a fourth mapping relationship between domain names and IP addresses. For example, this extension component can be an operator. Suppose that client #1 (an example of the first client) in Kubernetes cluster #1 needs to access service #C. Client #1 can first send request message #1 (an example of the third request message) to the extension component. This request message #1 carries the domain name of service #C (an example of the first domain name). This request message #1 is used to request the IP address corresponding to service #C. After receiving this request message, the extension component, based on its configuration...The fourth mapping relationship determines that the IP address corresponding to service #C is IP address #1, and sends a response message #1 (an example of the first response message) to client #1. This response message #1 carries the IP address #1 corresponding to service #C. For example, after obtaining the IP address corresponding to service #C, client #1 sends a request message #2 (an example of the first request message) to application gateway #1. Request message #2 carries IP address #1 and is used to request access to that IP address. Based on the received request message #2 and the received configuration information #1 from the gateway (e.g., including the first mapping relationship, the second mapping relationship, and the third mapping relationship), the first application gateway determines that the identifier of the service corresponding to IP address #1 is service #C based on the first mapping relationship, determines that service #C is located in the K8s cluster #2 based on the second mapping relationship, and determines that the K8s cluster #2 is associated with application gateway #2 (an example of the first application gateway) based on the third mapping relationship. 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. Furthermore, based on the second mapping relationship, it determines that service #C is provided by pod #7 (the second pod) on node #4 (an example of the second worker node) in cluster #2. Therefore, application gateway #2 sends request message #3 (an example of the second request message) to pod #7 to request access to service #C. Figure 5 illustrates a schematic diagram of service access by the client. As shown in Figure 5, the client in Kubernetes 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 achieving cross-cluster service access. As can be seen from Figure 5, the cross-Kubernetes cluster service access method provided in this application can uniformly forward service access requests to the application gateway corresponding to the Kubernetes cluster (e.g., application gateway #1), which can perform load balancing or governance. In this application, the application gateway can provide the IP address of the pod providing the target service based on the received service access request, and encapsulate the service access request message (e.g., using a virtual extensible local area network, VXLAN) before sending it to the application gateway (e.g., application gateway #2) corresponding to the Kubernetes cluster where the target service resides. This application gateway only performs routing and does not handle load balancing. This can also be understood as the data plane only needing to perform load balancing once, avoiding the load imbalance problem caused by multiple load balancing operations. 7 WO 2024 / 234764 PCT / CN2024 / 077764 As can be seen from the above description, in this application, two new functions are added to each tenant's Kubernetes cluster, one of which is...Client service access requests can be forwarded to the application gateway corresponding to the cluster. For example, this functionality can be implemented by a proxy component in the Kubernetes cluster, as shown in Figure 6. The proxy component can be the route-agent component in the figure. This route-agent can also monitor services and pods in other Kubernetes clusters and forward service access requests to the application gateway. Alternatively, this functionality can be implemented using the standard Kubernetes cluster application programming interface (API). For instance, if a Kubernetes cluster implements this API, there is no need to deploy an additional proxy component to implement this functionality. The API's custom resource definitions (CRDs) are defined as follows: "destinations" represents a list of destination network segments; "next-hop" represents next-hop information. These can be understood as 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 accessible across clusters need to be automatically injected into the tenant's Kubernetes cluster to achieve automatic service access. For example, this function can be implemented through an extension component, or through a proxy component to resolve the service domain names of other sites. As shown in Figure 7, the proxy component can be the Domain Name System (DNS) agent in Figure 7. For example, the application gateway in this application can be a centralized gateway, such as one that can be pre-deployed. For example, it can be deployed in a virtual private cloud (VPS) on the cloud. In a VPC, the application gateway can be deployed in a traditional data center or in a cloud VPC. For example, a tenant's Kubernetes cluster can also be deployed in a VPC, with the VPC where the application gateway resides and the VPC where the tenant's Kubernetes cluster resides automatically connected via the local controller. Alternatively, the application gateway can be deployed in a traditional data center, and the tenant's Kubernetes cluster can also be deployed in a traditional data center. The application gateway's network and the tenant's Kubernetes network can be pre-configured for connectivity via the physical network. After the application gateway is deployed, it can be managed by the management plane. Each resource pool has a corresponding application gateway. After the application gateway cluster is deployed and the tenant's Kubernetes cluster in the resource pool is added to the cluster group, it is scheduled by the management plane. For example, a mapping relationship between the application gateway and the application gateway can be configured. At this time, cross-cluster service access requests in the tenant's Kubernetes cluster can be uniformly forwarded to the corresponding application gateway. As described above, Figure 8 shows a schematic diagram of a system architecture applicable to this 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. Among them, the "orchestration layer" is used to provide a service console.This facilitates automatic service discovery and network interconnection for tenants using services across Kubernetes clusters. For example, the orchestration layer can be used for creating cluster groups, service management, service gateway management, canary releases, service traffic management, service security, site management, and gateway management. The "global control layer," also known as the "global controller," is responsible for distributing tenant configurations to various 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," can manage Kubernetes clusters within a site locally. One 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 clusters and application gateways. In this application, the global control layer and local control layer can be separated in their management. The global control layer has unified logic, while the local control layer provides localized management, partial autonomy, and high reliability. The local control layer can interface with the tenant's Kubernetes management plane and the application gateway, thereby enabling data plane connectivity. The "data plane forwarding layer" receives the configuration from the local controller and is responsible for forwarding service access requests across the Kubernetes cluster, including load balancing and other governance functions. As mentioned earlier, in this application, the pod is the entity providing the service. Service access requests are load-balanced through the application gateway and ultimately forwarded to the pod. Pods are elastically scalable. Changes to pods (e.g., changes in pod location or the addition of a pod) require notification to the application gateway so that the application gateway can correctly forward service method requests to the pod. Pods are managed by the tenant's Kubernetes cluster and require the extended components (e.g., operators) in the tenant's Kubernetes cluster to notify the local controller. The local controller then sends the updated routing information to the local application gateway and notifies the global controller. The global controller then sends the information to the local controllers of other clusters in the cluster group, and the local controllers then notify the application gateway to send the routing information for the pods. Based on the above scheme, in this application, by configuring the created cluster group by the tenant, the gateway can send third configuration information to each application gateway. This allows the first application gateway, upon receiving a service access request from a client in the first cluster, to directly forward the request to the corresponding application gateway in other clusters based on the obtained third configuration information, thereby ensuring that the tenant can access services within other clusters. This application enables automatic service communication between different clusters, achieving automatic network connectivity across clusters. Compared to the method of tenants statically and manually configuring the network, this is more convenient, improves the user's business experience, and avoids the use of sidecars for cross-cluster service communication, simplifying management and saving management costs. It is understood that the term "and / or" in this document is merely a description of the association relationship between related objects, indicating that three relationships can exist.For example, A and / or B can represent three cases: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, the character " / " in this document generally indicates an "or" relationship between the preceding and following objects. Those skilled in the art should recognize that, based on the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or computer software-driven hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art 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. Embodiments of this application can divide the device into functional modules according to the above method examples. For example, each function can be divided into separate functional modules, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this embodiment is illustrative and only represents one logical functional division. In actual implementation, other division methods may exist. The following explanation uses the division of functional modules according to their respective functions as an example. Figure 9 is a schematic block diagram of the device 900 provided in this embodiment. As shown, the computing device 900 may include: a transceiver module 910 and a processing module 920. Each of these modules is used to execute the respective steps of the aforementioned methods, which will not be elaborated further here. It should also be understood that the device 900 here is embodied in the form of a functional unit. The term "unit" here can refer to an application-specific integrated circuit (ASIC), electronic circuitry, 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 circuitry, and / or other suitable components supporting the described functions. The device 900 of the above-described schemes has the function of implementing the corresponding steps of the above-described method 300. The functions can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions; for example, the determining unit can be replaced by a processor to execute the transmit / receive operations and related processing operations in each method embodiment. Furthermore, the determining unit can be a processing circuit. In one possible implementation, device 900 can be the device applied in a cloud management platform in the above method 300, which is used to execute the actions in method 300. In another possible implementation, device 900 can be the cloud management platform in method 300, which is used to execute...Perform the actions described in method 300 above. It should be noted that the device in Figure 9 can be the cloud management platform (or the device within the cloud management platform) in the aforementioned method embodiments, or it can be the chip or chip system corresponding to the cloud management platform (or the device within 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. No limitation is made here. Figure 10 is a schematic block diagram of another device 1000 provided in this application embodiment. As shown, the device 1000 includes at least one processor 1020. The processor 1020 is coupled to a memory and is used to execute instructions stored in the memory to send and / or receive signals. Optionally, the device 1000 also includes a memory 1030 for storing instructions. Optionally, the device 1000 also includes a transceiver 1010, and the processor 1020 controls the transceiver 1010 to send and / or receive signals. It should be understood that the processor 1020 and memory 1030 can be combined into a processing device, with the processor 1020 executing the program code stored in the memory 1030 to achieve the above functions. Specifically, the memory 1030 can be integrated into the processor 1020 or independent of it. It should also be understood that the transceiver 1010 can include a transceiver (or receiver) and a transmitter (or transmitter). The transceiver may further include wires, and the number of wires can be one or more. The transceiver 1010 can be a communication interface or an interface circuit. Specifically, the processor 1020 in device 1000 can correspond to the processing module 920 in device 900. The transceiver 1010 in device 1000 can correspond to the processing module 910 in device 900. As one solution, device 1000 is used to implement the steps corresponding to the device applied in the cloud management platform in the above method 300 embodiments. As another option, the device 1000 is used to implement the steps corresponding to the cloud management platform in the above method 300 embodiment. For example, the processor 1020 is used to execute the computer program or instructions stored in the memory 1030 to implement the various steps in the above method 300. Figure 11 is a schematic diagram of the architecture of a computing device cluster provided in an embodiment of this application. The computing device cluster includes at least one computing device. The computing device can 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 can also be a terminal device such as a desktop computer, a laptop computer, or a smartphone. As shown in Figure 11, the computing device cluster includes at least one computing device 1100. The memory in one or more computing devices 1100 in the computing device clusterThe memory 1130 of one or more computing devices 1100 in the computing device cluster may store the same instructions for performing the actions executed by the cloud management platform (or the device in the cloud management platform) in the method 300 described in the above embodiment. 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 performing the actions executed by the cloud management platform (or the device in the cloud management platform) in the method 300 described in the above embodiment. In other words, a combination of one or more computing devices 1100 can jointly execute the instructions for performing the actions executed by the cloud management platform (or the device in the cloud management platform) described in the above embodiment. It should be noted that the memory 1130 of different computing devices 1100 in the computing device cluster may store different instructions, which are used to execute partial functions of computing device Π00 respectively. That is, the instructions stored in the memory 1130 of different computing devices Π00 can implement the functions of one or more modules of the transceiver module 910 and the processing module 920. Alternatively, the memory 1130 in different computing devices 1100 within the computing device cluster can store different instructions, each used to execute a portion of the functions of the cloud management platform (or devices within the cloud management platform) corresponding to the aforementioned devices 900-1000. That is, the instructions stored in the memory 1130 of different computing devices 1100 can implement the functions of one or more modules in the transceiver module 910 and processing module 920. In some possible implementations, one or more computing devices in the computing device cluster can be connected via a network. This network can be a wide area network (WAN) or a local area network (LAN), etc. Figure 12 illustrates one possible implementation. As shown in Figure 12, two computing devices 1200A and 1200B are connected via a network. Specifically, they are connected to the network through the communication interfaces in each computing device. It should be understood that the function of computing device 1200A shown in Figure 12 can also be performed by multiple computing devices 1100. Similarly, the function of computing device 1200B can also be performed by multiple computing devices 1100. This embodiment also provides a computer program product containing instructions. The computer program product may be software or program products containing instructions, capable of running on a computing device cluster or stored in any usable medium. When run by the computing device cluster, it causes the computing device cluster to perform the methods provided above, or causes the computing device cluster to implement the functions of the apparatus provided above. This embodiment also provides a computer-readable storage medium. The computer-readable storage medium may be any usable medium that a computing device can store, or a data storage device such as a data center containing one or more usable media. The usable medium may be a magnetic medium.The computer-readable storage medium includes instructions that, when executed on a computing device, cause the computing device cluster to perform the methods provided above. This embodiment also provides a computer-readable storage medium, which can be any available medium that the computing device can store or a data storage device such as a data center containing one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state drive). The computer-readable storage medium includes instructions that, when executed by a cluster of computing devices, cause the cluster of computing devices to perform the methods provided above. Those skilled in the art will recognize that the units and algorithm steps of the various examples 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 implemented in hardware or software depends on the specific application and design constraints of the technical solution. Skilled professionals 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. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. 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 illustrative; for example, the division of units is merely a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces; the indirect coupling or communication connection of devices or units may be electrical, mechanical, or other forms. The units described as separate components may or may not be physically separate; 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 the units can be selected to achieve the purpose of this embodiment according to actual needs. In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.If the aforementioned functions are implemented as 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 this application, in essence, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes: USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks, and various other media capable of storing program code. The above descriptions are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of protection of the claims. 11 WO 2024 / 234764 PCT / CN2024 / 077764 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, the cloud service system including multiple clusters, each cluster including at least a client and at least one worker node, each worker node including at least one pod, each pod being used to provide services, the method comprising: receiving first configuration information from a tenant, the first configuration information being used to instruct the creation of a cluster group for the multiple 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, the second configuration information being used to instruct the creation of a gateway in the cluster group; creating the gateway in the cluster group according to the second configuration information; The system receives third configuration information from the tenant. This third configuration information includes: a first mapping relationship between the service name and the corresponding access address of the service included in each cluster; a second mapping relationship between the service name and the corresponding cluster information of the service included in each cluster; and a third mapping relationship between each cluster and its corresponding application gateway. The cluster information is used to identify the cluster. The system then configures the third configuration information to the gateway, which in turn sends the third configuration information to each cluster.The corresponding application gateway is used to access services based on the client's request message and the third configuration information. 2. The method according to claim 1, wherein 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. 3. The method according to claim 1 or 2, wherein the cluster information includes: the name of the cluster, the name of the worker node in the cluster, and the name of the pod in the worker node. 4. The method according to any one of claims 1 to 3, characterized in that the plurality of clusters includes a first cluster and a second cluster, the first cluster includes a first client, the first cluster is associated with a first application gateway, and the method further includes: the first client obtaining a first IP address corresponding to a first domain name; the first client sending a first request message to the first application gateway, the first request message carrying the first IP address, the first request message being used to request access to the first IP address; the first application gateway determining, based on the first request message and the first mapping relationship, that the service identifier corresponding to the first IP address is a first identifier, determining, based on the second mapping relationship, that the first identifier is an identifier corresponding to a service in the second cluster, and determining, based on the third mapping relationship, that the second cluster is associated with a second application gateway; and the first application gateway sending the first request message to the second application gateway. 5. The method according to claim 4, characterized in that the method further includes: the gateway sending 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 determining, 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 determining, based on the second mapping relationship, that the first identifier corresponds to the second pod in the second worker node of the second cluster; the second application gateway sending a second request message to the second pod, the second request message being 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 comprises a first module, the first module being configured with a fourth mapping relationship between the domain name and the IP address, the first module being used for domain name resolution; the first client obtaining the first IP address corresponding to the first domain name includes: the first client sending a third request message to the first module, the third request message carrying the first domain name, the third request message being used to request obtaining the Internet Protocol (IP) address corresponding to the first domain name;The first client receives a first response message from the first module, the first response message carrying the first IP address, the first IP address being determined by the first module. 8. An apparatus, applied to a cloud management platform in a cloud service system, the cloud service system including multiple clusters, each cluster including at least a client and at least one worker node, each worker node including at least one pod, each pod used to provide services, the apparatus including: a transceiver module and a processing module, the transceiver module being configured to: receive first configuration information from a tenant, the first configuration information being used to instruct the creation of a cluster group for the multiple clusters; the processing module being configured to: create the cluster group according to the first configuration information, wherein the cluster group includes the multiple clusters; the transceiver module being configured to: receive second configuration information from the tenant, the second configuration information being used to instruct the creation of a gateway in the cluster group; the processing module being configured to: create the gateway in the cluster group according to the second configuration information; The transceiver module is configured to receive third configuration information from the tenant, the third configuration information including: a first mapping relationship between the service name and the corresponding access address of the service included in each cluster, a second mapping relationship between the service name and the corresponding cluster information of the service included in each cluster, and a third mapping relationship between each cluster and the application gateway corresponding to each cluster, wherein the cluster information is used to determine the cluster; the processing module is configured to configure the third configuration information to the gateway, the gateway is configured to send the third configuration information to the application gateway corresponding to each cluster, and the application gateway is configured to access the service according to the client's request message and the third configuration information. 9. The apparatus according to claim 8, wherein 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 apparatus according to claim 8 or 9, wherein the cluster information includes: the name of the cluster, the name of the worker node in the cluster, and the name of the pod in the worker node. 11. The apparatus according to any one of claims 8 to 10, characterized in that the plurality of clusters includes a first cluster and a second cluster, the first cluster includes a first client, the first cluster is associated with a first application gateway, the first client is configured to obtain a first IP address corresponding to a first domain name; the first client is configured to send a first request message to the first application gateway, the first request message carrying the first IP address.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, the service identifier corresponding to the first IP address is a first identifier, according to the second mapping relationship, the first identifier is determined to be the identifier corresponding to a service in the second cluster, and according to the third mapping relationship, 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 apparatus according to claim 11, wherein the gateway is used to send the third configuration information to the first application gateway and the second application gateway. 13. The apparatus according to claim 12, wherein the second application gateway is used to determine, according to the first IP address and the first mapping relationship carried in the first request message, the service identifier corresponding to the first IP address is the first identifier, and according to the second mapping relationship, the first identifier corresponds to a second pod in the second worker node of the second cluster; the second application gateway is used to send a second request message to the second pod, the second request message being used to request access to the service corresponding to the first identifier. 14. The apparatus according to any one of claims 11 to 13, wherein the first cluster further comprises a first module, the first module being configured with a fourth mapping relationship between the domain name and the IP address, the first module being used for domain name resolution, and the first client being used to obtain a first IP address corresponding to a first domain name, comprising: the first client being used to send a third request message to the first module, the third request message carrying the first domain name, the third request message being used to request the acquisition of the Internet Protocol IP address corresponding to the first domain name; and the first client being used to receive a first response message from the first module, the first response message carrying the first IP address, the first IP address being determined by the first module. 15. A computing device, comprising a processor and a memory, the processor executing instructions in the memory to cause the processor to perform the method according to any one of claims 1 to 7. 16. A computing device cluster, comprising at least one computing device, each computing device comprising a processor and a memory; the processor of the at least one computing device being used to execute instructions stored in the memory of the at least one computing device to cause the computing device cluster to perform 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 cluster of computing devices, the cluster of computing devices causes the cluster of computing devices to perform the method as described in any one of claims 1 to 7. 13 WO 2024 / 234764PCT / CN2024 / 077764 18. A computer-readable storage medium, characterized in that it comprises computer program instructions, which, when executed by a cluster of computing devices, perform the method as described in any one of claims 1 to 7. 14 WO 2024 / 234764 PCT / CN2024 / 077764 Cloud System Diagram 2 1 / 6 WO 2024 / 234764 PCT / CN2024 / 077764 Method 300 Figure 3 2 / 6 WO 2024 / 234764 PCT / CN2024 / 077764 Inch Country 3 / 6 WO 2024 / 234764 PCT / CN2024 / 077764 Figure 5 Figure 7 4 / 6 WO 2024 / 234764 PCT / CN2024 / 077764 Application Network Service I~Cluster Group_II Service Management II Service Gateway Management II Gray Release II Traffic Governance II Service Security II Site Management II Gateway Management I Orchestration Layer------ ------------------ ------- ------------------------------------ Figure 8 Device 900 Transceiver Module 910 Processing module 920 Figure 9 Device 1000 Figure 10 5 / 6 WO 2024 / 234764 PCT / CN2024 / 077764 Figure 11 Figure 12 6 / 6 INTERNATIONAL SEARCH REPORT International application No. PCT / CN2024 / 077764 A. CLASSIFICATION OF SUBJECT MATTER H04L 67 / 51(2022.01)1 According to International Patent Classification (IPC) or to both national classification and IPC B. FIELDS SEARCHED Minimum documentation searched (classification system followed by classification symbols) IPC:H04L Documentation searched other than minimum documentation to the extent that such documents are included in thefields searched Electronic data base consulted during the international search (name of data base and, where practicable, search terms used) CNABS, CNTXT, CNKI, VEN, EPTXT, USTXT, WOTXT, IEEE: address correspondence, service relationship, cross-cluster, matching, gateway service mapping, address, business, cluster, corresponding, cross, gateway, mapping, match, service C. DOCUMENTS CONSIDERED TO BE RELEVANT Category* Citation of document, with indication, where appropriate, of the relevant passages Relevant to claim No. A CN 113783774 A (BEIJING SHAREIT INFORMATION TECHNOLOGY CO., LTD.) 10 December 2021 (2021-12-10) description, paragraphs

[0058] -

[0062] 1-18 A CN 110138862 A (BEIJING BYTEDANCE NETWORK TECHNOLOGY CO., LTD.) 16 August 2019 (2019-08-16) entire document 1-18 A CN 114398176 A (BEIJING KINGSOFT CLOUD NETWORK TECHNOLOGY CO., LTD.) 26 April 2022 (2022-04-26) entire document 1-18 A CN 115866061 A (NINGBO GEELY AUTOMOBILE RESEARCH & DEVELOPMENT CO., LTD.) 28 March 2023 (2023-03-28) entire document 1-18 A US 2021232440 A1 (HEWLETT PACKARD ENTERPRISEDEVELOPMENT LP) 29 July 2021 (2021-07-29) entire document 1-18 | | Further documents are listed in the continuation of Box C. | / 1 See patent family annex. * Special categories of cited documents: “T" later document published after the international filing date or priority “A" document defining the general state of the art which is not considered date and not in conflict with the application but cited to understand the to be of paiticulai' relevance principle or theory underlying the invention "D” document cited by the applicant in the international application “χ” document of particular relevance; the claimed invention cannot be “E” eailier application or patent but published on or after the international considered novel or cannot be considered to involve an inventive step filing date when the document is taken alone “L" document which may thi'ow doubts on priority claim(s) or which is “Y" document of paiticulai' relevance; the claimed invention cannot be cited to establish thepublication date of another citation or other considered to involve an inventive step when the document is special reason (as specified) combined with one or more other such documents, such combination "O” document refen'ing to an oral disclosure, use, exhibition or other being obvious to a person skilled in the art means document member of the same patent family "P” document published prior to the international filing date but later than the priority date claimed Date of the actual completion of the international search 13 May 2024 Date of mailing of the international search report 20 May 2024 Name and mailing address of the ISA / CN China National Intellectual Property Administration (ISA / CN) China No. 6, Xitucheng Road, Jimenqiao, Haidian District, Beijing 100088 Authorized officer Telephone No. Form PCT / ISA / 210 (second sheet) (July 2022) International application No. PCT / CN2024 / 077764 INTERNATIONAL SEARCH REPORT Information on patent family members Patent document cited in searchReport Publication date (day / month / year) Patent family member(s) Publication date (day / month / year) CN 113783774 A 10 December 2021 None CN 110138862 A 16 August 2019 None CN 114398176 A 26 April 2022 None CN 115866061 A 28 March 2023 None US 2021232440 A1 29 July 2021 US 11847503 B2 19 December 2023 Form PCT / ISA / 210 (patent family annex) (July 2022) International Application Number PCT / CN2024 / 077764 International Search Report A. Subject Classification H04L 67 / 51 (2022.01) 1 B. Minimum literature to be searched in the search field (indicating the classification system and classification number) IPC: H04L Electronic databases consulted during international searches (database name and search terms used, if applicable) CNABS, CNTXT, CNKI, VEN, EPTXT, USTXT, WOTXT, IEEE: address correspondence, service, relationship, cross-cluster matching gateway service, mapping, address, business, cluster, corresponding, cross, gateway, mapping, match, service c. Relevant document types * Referenced documents, indicating relevant paragraphs where necessary Relevant claims A CN 113783774 A (Beijing Kuailejia Information Technology Co., Ltd.) December 10, 2021 (2021-12-10) Specification paragraphs

[0058] -

[0062] 1-18 A CN 110138862 A (Beijing ByteDance Network Technology Co., Ltd.) August 16, 2019 (2019-08-16) Full Text 1-18 A CN 114398176 A (Beijing Kingsoft Cloud Network Technology Co., Ltd.) April 26, 2022 (2022-04-26) Full Text 1-18 A CN 115866061 A (Ningbo Geely Automobile Research and Development Co., Ltd.) March 28, 2023 (2023-03-)28) Full text 1-18 A US 2021232440 A1 (HEWLETT PACKARD ENTPR DEV LP) July 29, 2021 (2021-07-29) Full text 1-18 □ The remaining documents are listed on the continuation page in column C. *Specific types of cited documents: “A” Documents that are considered not particularly relevant and indicate the general state of the prior art. “D” Documents cited by the applicant in the international application. “E” Earlier applications or patents published on or after the international filing date. “L” Documents that may raise doubt about the priority claim, or documents cited to determine the publication date of another cited document, or documents cited for other specific reasons (as specifically stated). Documents involving □head disclosure, use, exhibition, or other disclosure. “P” Documents published before the international filing date but later than the claimed priority date. See the patent family appendix. "A document published after the application date or priority date, which does not conflict with the application, but is particularly different from the subsequent document for understanding the inventive theory or principle, is considered alone, and the claimed invention is deemed not novel or lacking inventiveness. A document particularly related to "Y" is also considered, and when the document is not combined with any of the other documents of the same class and such combination is obviously excessive to those skilled in the art, the claimed invention lacks inventiveness. International search of patent family documents: Date of actual completion: May 13, 2024. Name and mailing address of ISA / CN: China National Intellectual Property Administration, No. 6, Tucheng Road, Xijimenqiao, Haidian District, Beijing 100088, China. International search report mailing date: May 20, 2024. Authorized officer: Mu Jian. Telephone number: (+86) 0512-88995975. PCT / ISA / 210 Form (Page 2) (July 2022). International Application Number: PCT / CN2024 / 077764 International Search Report Information on Patent Family Publication Date of Patent Documents Cited in the Search Report (Year / Month / Day) Publication Date of Patent Family (Year / Month / Day) CN 113783774 A December 10, 2021 None CN 110138862 A August 16, 2019 None CN 114398176 A April 26, 2022 None CN 115866061 A March 28, 2023 None US 2021232440 A1 July 29, 2021 US 11847503 B2 December 19, 2023 PCT / ISA / 210 Form (Appendix to Patent Family) (July 2022) (19) *EP004701162A1* (11) EP 4 701 162 A1 (12) EUROPEAN PATENT APPLICATIONpublished in accordance with Art. 153(4) EPC (43) Date of publication: 25.02.2026 Bulletin 2026 / 09 (21) Application number: 24806125.1 (22) Date of filing: 20.02.2024 (51) International Patent Classification (IPC): H04L 67 / 51 (2022.01) (52) Cooperative Patent Classification (CPC): H04L 41 / 0803; H04L 67 / 10; H04L 67 / 30; H04L 67 / 51; H04L 67 / 63 (86) International application number: PCT / CN2024 / 077764 (87) International publication number: WO 2024 / 234764 (21.11.2024 Gazette 2024 / 47) (84) Designated Contracting States: AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC ME MK MT NL NO PL PT RO RS SE SI SK SM TR Designated Extension States: BA Designated Validation States: GE KH MA MD TN (30) Priority: 12.05.2023 CN 202310539823 12.10.2023 CN 202311324854 (71) Applicant: Huawei Cloud Computing Technologies Co., Ltd. Guiyang, Guizhou 550025 (CN) (72) Inventors: • ZHU, Na Guiyang, Guizhou 550025 (CN) • YAO, Bo Guiyang, Guizhou 550025 (CN) • YANG, Yi Guiyang, Guizhou550025 (CN) • ZHANG, Caizheng Guiyang, Guizhou 550025 (CN) (74) Representative: Epping - Hermann - Fischer Patentanwaltsgesellschaft mbH Schloßschmidstraße 5 80639 München (DE) (54) CROSS‑CLUSTER SERVICE ACCESS METHOD, AND APPARATUS (57) This application provides a method for cross- cluster service access and a computing apparatus. A tenant configures a created cluster group, and a gateway may send third configuration information to each applica- tion gateway, so that when receiving a service access request of a client in a first cluster, a first application gateway may directly forward, based on the obtained third configuration information, the service access re- quest to an application gateway corresponding to an- other cluster. In this way, it is ensured that the tenant can access a service in the another cluster, to implement automatic access between services in a plurality of clus- ters, thereby facilitating management and reducing man- agement costs. EP 4 70 1 16 2 A 1 Processedby Luminess, 75001 PARIS (FR) Description

[0001] This application claims priority to Chinese Patent Application No. 202310539823.0, filed with the China National Intellectual Property Administration on May 12, 2023 and entitled "METHOD AND APPARATUS FOR AUTOMATIC DISCOVERY OF CROSS-CONTAINER CLUSTER SERVICE AND AUTOMATIC NETWORK INTERWORKING", which is incorporated herein by reference in its entirety.

[0002] This application claims priority to Chinese Patent Application No. 202311324854.0, filed with the China National Intellectual Property Administration on October 12, 2023 and entitled "METHOD FOR CROSS-CLUSTER SERVICE ACCESS AND APPARATUS", which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0003] This application relates to the field of container application technologies, and more specifically, to a method for cross-cluster service access and an apparatus. BACKGROUND

[0004] K8s is a lightweight and scalable open-source platform for managing containerizedapplications and services. K8s enables automatic deployment and scaling of applications. K8s combines containers included in an application into a logical unit for easy management and discovery. K8s has properly resolved a problem of access between services (which may also be understood as applications) in a single cluster. However, K8s does not provide an automatic solution for access between services in a plurality of clusters. Currently, configuration can be performed only manually. The configuration is highly complex and inconvenient to manage, and errors may easily occur. Currently, an open-source service grid project supports cross-K8s cluster service access but is implemented in a sidecar (sidecar) manner. A sidecar container is deployed in each pod. Access between services in different clusters is forwarded to the sidecar container in an agent mode. Service governance is performed in the sidecar container. However, sidecar resource usage is high and management costs are high.

[0005] Therefore, a method for cross-cluster service access is needed, to implement automatic access between services in a plurality of clusters, thereby facilitating management and reducing management costs. SUMMARY

[0006] This application provides a method for cross-cluster service access, to implement automatic access between services in a plurality of clusters, thereby facilitating management and reducing management costs.

[0007] According to a first aspect, a method for cross-cluster service access is provided. The method may be applied to a cloud service system. The method may be performed by a cloud management platform (or an apparatus in a cloud management platform), or may be performed by a component (for example, a chip or a circuit) of a cloud management platform (or an apparatus in a cloud management platform).

[0008] In this application, the cloud service system includes a plurality of clusters, each cluster at least includes a client and at least one worker node, eachworker node includes at least one pod, and each pod is configured to provide a service.

[0009] The method includes: receiving first configuration information from a tenant, where the first configuration information indicates to create a cluster group for the plurality of clusters; creating the cluster group based on the first configuration information, where the cluster group includes the plurality of clusters; receiving second configuration information from the tenant, where the second configuration information indicates to create a gateway in the cluster group; creating the gateway in the cluster group based on the second configuration information; receiving third configuration information from the tenant, where the third configuration information includes: 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 the service name corresponding to the serviceincluded in each cluster and corresponding cluster information, and a third mapping relationship between each cluster and an application gateway, where the cluster information determines the cluster; and configuring the third configuration information to the gateway, where the gateway is configured to send the third configuration information to the application gateway corresponding to each cluster, and the application gateway is configured to perform service access based on a request message of the client and the third configuration information.

[0010] In this application, 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. The "cluster" in this application may be, for example, a K8s cluster.

[0011] In this application, for example, the "cluster information" may include: a name ofthe cluster, a name of the worker node in the cluster, and a name of the pod on the worker node. 2 EP 4 701 162 A1 5 10 15 20 25 30 35 40 45 50 55

[0012] Based on the foregoing technical solutions, this application provides a method for cross-cluster service access and a computing apparatus. The tenant configures the created cluster group, and the gateway may send the third configuration information to each application gateway, so that when receiving a service access request of a client in a first cluster, a first application gateway may directly forward, based on the obtained third configuration information, the service access request to an application gateway corresponding to another cluster, thereby ensuring that the tenant can access a service in the another cluster. In this application, the tenant performs configuration in the clusters, so that automatic service access between different clusters is implemented, that is, automatic network connection between the clusters isimplemented. In comparison with a manner in which a tenant statically and manually configures a network, this manner is more convenient, improves service experience of a user, and avoids using a sidecar to implement cross-cluster service access, thereby facilitating management and reducing management costs.

[0013] In a possible implementation, the plurality of 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 a 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 to access the first IP address; the first application gateway determines, based on the first request message and the first mapping relationship, that a serviceidentifier corresponding to the first IP address is a first identifier, determines, based on the second mapping relationship, that the first identifier is an identifier corresponding to a service in the second cluster, and determines, based on the third mapping relationship, that the second cluster is associated with a second application gateway; and the first application gateway sends the first request message to the second application gateway.

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

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

[0016] For example, the gateway may send all of the third configuration information to the application gateway corresponding to eachcluster.

[0017] For example, the gateway may determine, based on a service access request message of a client, configuration information that needs to be delivered and application gateways to which the required configuration information needs to be delivered. For example, if the gateway determines, based on a service access request message of a client, that the service access request is a request of a client in a cluster #1 to access a service #C in a cluster #2, the gateway may send configuration information #1 related to the service #C to only an application gateway #1 corresponding to the cluster #1 and an application gateway #2 corresponding to the cluster #2, where the configuration information #1 is partial configuration information in the third configuration information.

[0018] In a possible implementation, the method further includes: The second application gateway determines, based on 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 determines, based on the second mapping relationship, that the first identifier corresponds to a second pod in a second worker node in the second cluster; and the second application gateway sends a second request message to the second pod, where the second request message is used to request to access the service corresponding to the first identifier.

[0019] In a possible implementation, the first cluster further includes a first module, a fourth mapping relationship between the domain name and the IP address is configured on the first module, and the first module is configured to perform domain name resolution. That the first client obtains the first IP address corresponding to the first domain name includes: The first client sends a third request message to the first module, where the third request message carries the first domain name, and the third request message is used to request toobtain an Internet Protocol IP address corresponding to the first domain name; and 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.

[0020] In this application, the first module may be an extended module, for example, may be an operator module.

[0021] Based on the foregoing technical solutions, in this application, the first module may implement domain name resolution, and the application gateway may send the service access request to a gateway corresponding to another cluster, thereby implementing cross-cluster service access.

[0022] According to a second aspect, this application provides an apparatus, where the apparatus is configured to perform the method in the first aspect. Specifically, the apparatus may include units and / or modules configured to perform a method for cross-cluster service accessmethod for cross-cluster serviceaccessprovided in this application, for example, a transceiver unit and / or a processing unit. In this application, the apparatus is applied to a cloud management platform. Alternatively, the apparatus is a cloud management platform.

[0023] According to a third aspect, this application provides an apparatus. The apparatus includes: at least one processor, configured to execute a computer program or instructions stored in a memory, to perform the method in the first 3 EP 4 701 162 A1 5 10 15 20 25 30 35 40 45 50 55 aspect. Optionally, the apparatus further includes the memory, configured to store the computer program or the instructions. Optionally, the apparatus further includes a communication interface, and the processor reads, via the communication interface, the computer program or the instructions stored in the memory.

[0024] In an implementation, the apparatus is an apparatus that is used in a chip to implement functions of the foregoing method for cross-cluster serviceaccessmethod for cross-cluster service accessand that is applied to a cloud management platform. Alternatively, the apparatus is a cloud management platform.

[0025] In another implementation, the apparatus is a chip, a chip system, or a circuit that is used in a chip to implement the functions of the foregoing method for cross-cluster service accessmethod for cross-cluster service accessand that is applied to a cloud management platform.

[0026] According to a fourth aspect, this application provides a processor, including an input circuit, an output circuit, and a processing circuit. The processing circuit is configured to receive a signal by using the input circuit, and transmit a signal by using the output circuit, so that the processor performs the method in the first aspect.

[0027] In a specific implementation process, 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 atransistor, a gate circuit, a trigger, any logic circuit, or the like. An input signal received by the input circuit may be received and input by, for example, including but not limited to, a transceiver. A signal output by the output circuit may be output to, for example, including but not limited to, a transmitter and transmitted by the transmitter. The input circuit and the output circuit may be a same circuit, where the circuit is used as the input circuit and the output circuit separately at different moments. Specific implementations of the processor and the circuits are not limited in embodiments of this application.

[0028] Unless otherwise specified, or if operations such as sending, and obtaining / receiving related to the processor do not contradict an actual function or internal logic of the operations in related descriptions, the operations may be understood as operations such as outputting, receiving, and inputting of the processor, or may be understood as operations such assending and receiving performed by a radio frequency circuit and an antenna. This is not limited in this application. According to a fifth aspect, a processing device is provided, including a processor and a memory. The processor is configured to read instructions stored in the memory, receive a signal by using a transceiver, and transmit a signal by using a transmitter, to perform the method in the first aspect. Optionally, there are one or more processors, and there are one or more memories.

[0029] Optionally, the memory may be integrated with the processor, or the memory and the processor are separately disposed.

[0030] In a specific implementation process, the memory may be a non-transitory (non-transitory) memory, such as a read-only memory (read-only memory, ROM). The memory and the processor may be integrated into a same chip, or may be separately disposed in different chips. A type of the memory and a manner in which the memory and the processor are disposed are not limited inthis embodiment of this application.

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

[0032] The processing device according to the fifth aspect may be one or more chips. The processor in the processing device may be implemented by using hardware, or may be implemented by using software. When the processor is implemented by using hardware, the processor may be a logic circuit, an integrated circuit, or the like. When the processor is implemented by using software, the processor may be ageneral-purpose processor, and is implemented by reading software code stored in the memory. The memory may be integrated into the processor, or may be disposed outside the processor and exist independently.

[0033] According to a sixth aspect, this application provides a computing device cluster, including at least one computing device. Each computing device includes 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 in any one of the first aspect or the possible implementations of the first aspect.

[0034] Optionally, the processor may be a general-purpose processor, and may be implemented by using hardware or software. When the processor is implemented by using hardware, the processor may be a logic circuit, an integrated circuit, or the like. When the processor is implemented by using software, theprocessor may be a general-purpose processor, and is implemented by reading software code stored in the memory. The memory may be integrated into the processor, or may be disposed outside the processor and exist independently.

[0035] According to a seventh aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores program code for a device to execute, and the program code is configured to perform the method in the first aspect.

[0036] According to an eighth aspect, a computer program product including instructions is provided. When the computer program product is run on a computer, the computer is enabled to perform the method in the first aspect. 4 EP 4 701 162 A1 5 10 15 20 25 30 35 40 45 50 55

[0037] According to a ninth aspect, a chip system is provided, including a processor, configured to invoke and run a computer program from a memory so that a device in which the chip system is installed performs the method in the first aspect.

[0038] According to a tenth aspect, a cloud service system is provided. The cloud service system includes a cloud management platform, and a computing node and / or a network node. The cloud management platform is configured to perform the method in any one of the possible implementations of the first aspect. The computing node is configured to perform related actions of a first client, a first application gateway, and a second application gateway. BRIEF DESCRIPTION OF DRAWINGS

[0039] FIG. 1 is a diagram of a K8s cluster architecture according to this application; FIG. 2 is a diagram of a cloud service scenario to which this application is applicable; FIG. 3 is a schematic flowchart of a method 300 for cross-cluster service access according to this application; FIG. 4 is another schematic flowchart of a method for cross-cluster service access according to this application; FIG. 5 is still another schematic flowchart of a method for cross-cluster service access according to this application;FIG. 6 is another diagram of a K8s cluster architecture according to this application; FIG. 7 is still another diagram of a K8s cluster architecture according to this application; FIG. 8A and FIG. 8B are diagrams of a system architecture to which this application is applicable; FIG. 9 is a block diagram of an apparatus 900 according to this application; FIG. 10 is a block diagram of an apparatus 1000 according to this application; FIG. 11 is a diagram of an architecture of a computing apparatus cluster according to this application; and FIG. 12 is a diagram of connection between computing apparatuses 1200A and 1200B via a network according to this application. DESCRIPTION OF EMBODIMENTS

[0040] The following describes technical solutions of this application with reference to the accompanying drawings. 1. K8s

[0041] K8s (Kubernetes) is an example of a distributed system having a proper architecture. It treats each machine in a cluster as a part of a single resource pool. K8s has twolayers: a master node (master) and a worker node (node). The master node or main node includes a control plane and worker node applications. A K8s cluster includes many master nodes and worker nodes.

[0042] During physical division of K8s, hosts are classified into two types: a master node and a node (node). The master node mainly performs functions such as cluster resource scheduling and control. The node (node) is mainly a node used for running a container, namely, a node used for running a service. The master stores various metadata. The node (node) is a worker node, and is mainly used for running various services. The node (node) communicates with the master node at regular time, and reports information via a kubelet process. 2. Pod

[0043] A pod is a minimum unit created or deployed in K8s. One pod represents a process that is running in a cluster. One pod includes one or more containers. The containers in the pod share network, storage, and computing resources, and run on a samedocker host. A plurality of containers may run in one pod. In a production environment, generally a single container forms a pod, or a plurality of containers that are closely associated with and complementary to each other form a pod. One pod can run on only one host, but there may be a plurality of pods on one host. 3. Container

[0044] A container is a runnable software package, which contains a complete executable program, including: code, a run-time application and a system library, and default values of all important settings. In the container, the application runs in an independent environment. This environment is usually provided by a container engine. Containers use a kernel of a host system. An application and dependencies of the application are packaged together to run as a container. Resources are shared between the containers and the host system. Therefore, the containers are usually more lightweight than virtual machines, and it is easier to start and stop the containers.5 EP 4 701 162 A1 5 10 15 20 25 30 35 40 45 50 55 4. Service (service)

[0045] In a K8s cluster, although an independent Internet Protocol (Internet protocol, IP) address is allocated to each pod, the pod has a life cycle (the pod may be created and is no longer started after being destroyed) and the IP address may also disappear at any time as the pod is destroyed due to a service change.

[0046] A "service" is used just to resolve this problem. A service in K8s may be understood as a gateway layer, and may be considered as an external access interface and a traffic balancer for a group of pods that provide the same service. A service that a client needs to access is a service object. Each service has a fixed virtual IP address, which may be automatically and dynamically bound to a back-end pod. For all network requests of the service, the virtual IP address of the service is directly accessed, and the service automatically forwards the requests to a back end. In addition to providing astable external access manner, the service further provides a load balancing (load balance) function. Request traffic is automatically distributed to all services at the back end. The service may perform horizontal scaling, which is transparent to a customer.

[0047] As a core of the K8s service, the service shields service details and externally presents a service interface in a unified manner, thereby really implementing a "micro service". For example, three replicas, which mean three pods, are deployed for a service #A, and a tenant needs to pay attention to only one ingress of the service and does not need to care about which pod should be exactly requested. This has the following advantages: The external tenant does not need to be aware of an IP address change caused by unexpected failure of a service on a pod or pod restart by K8s; and the external tenant does not need to be aware of an IP address change caused by pod replacement due to upgrade or a service change.

[0048] FIG. 1is a diagram of an internal system architecture of K8s according to this application. FIG. 1 shows two K8s clusters, and a K8s cluster #1 is used as an example for description. The cluster includes two worker nodes: a node #1 and a node #2. The node #1 includes two pods: a pod #11 and a pod #12. The pod #11 includes two containers, and one of the containers is a container #111. The pod #12 includes three containers, and one of the containers is a container #121. The node #2 in the K8s cluster #1 may be understood in a similar manner, and the K8s cluster #2 may be understood in a similar manner. Details are not described again. Currently, access between services in a plurality of clusters may be implemented by manually configuring information such as an IP address of a gateway. The configuration is highly complex and inconvenient to manage, and errors may easily occur. In other words, a network between nodes in different clusters cannot be automatically connected, and manualconfiguration is needed instead. For example, a network between the node #1 in the K8s cluster #1 and a node #3 in the K8s cluster #2 in FIG. 1 cannot be automatically connected, and some IP address information needs to be manually configured to implement cross-cluster service access.

[0049] In view of this, this application provides a service access method, to implement automatic access between services in different K8s clusters, and implement automatic network connection between the K8s clusters. In comparison with a manner in which a tenant statically and manually configures a network, this method is more convenient, improves user service experience, and avoids using a sidecar to implement cross-cluster service access, thereby facilitating management and reducing management costs

[0050] The method for cross-cluster service accessmethod for cross-cluster service accessprovided in embodiments of this application may be applied to a cloud service scenario, and a cloud managementplatform in the cloud service scenario performs the method. The following first describes a cloud service scenario in detail with reference to FIG. 2.

[0051] FIG. 2 is a block diagram of a cloud service scenario to which an embodiment of this application is applicable. As shown in FIG. 2, the cloud service scenario may include: a cloud management platform 210, an Internet 220, and a client 230.

[0052] As shown in FIG. 2, the cloud management platform 210 is configured to manage infrastructure that provides a plurality of cloud services. The infrastructure includes a plurality of cloud data centers, each cloud data center includes a plurality of servers, and each server includes a cloud service resource to provide a corresponding cloud service for a tenant. In this embodiment of this application, the cloud service resource may be a cloud database.

[0053] The cloud management platform 210 may be arranged in a cloud data center, and may provide an access interface (for example, aninterface or an application programming interface (application programming interface, API)). The tenant may operate a remote access interface of the client 230 to register a cloud account and a 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 the password, the tenant may further pay on the cloud management platform 210 to select and purchase a virtual machine with a specific specification (a processor, a memory, or a disk). After the payment and purchase are successful, the cloud management platform 210 provides a remote login account and a password of the purchased virtual machine, and the client 230 may remotely log in to the virtual machine, and install and run an application of the tenant in the virtual machine. Therefore, the tenant may create, manage, log in to, and operate a virtual machine in the cloud data center by using the cloud managementplatform 210.

[0054] Functions of the cloud management platform 210 include, but are not limited to, a tenant console, a computing management service, a network management service, a storage management service, an authentication service, and an image management service. The tenant console provides an interface or an API to interact with the tenant. The computing 6 EP 4 701 162 A1 5 10 15 20 25 30 35 40 45 50 55 management service is used to manage servers and bare metal servers running virtual machines and containers. The network management service is used to manage network services (such as gateways and firewalls). 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. The tenant may log in to the cloud management platform 210 by using the client 230 over the Internet 220, to manage a leased cloudservice.

[0055] In this application, the K8s cluster may be deployed on a public cloud, a private cloud, or a conventional data center, or a physical machine. This is not limited.

[0056] FIG. 3 is a schematic flowchart of a method 300 for cross-cluster service access according to this application. For example, the method may be performed by the cloud management platform in the cloud service system shown in FIG. 2. As described previously, the cloud service system includes a plurality of clusters, each cluster at least includes a client and at least one worker node, each worker node includes at least one pod, and each pod is configured to provide a service. As shown in FIG. 3, the method includes the following steps.

[0057] 310: Receive first configuration information from a tenant, where the first configuration information indicates to create a cluster group for a plurality of clusters.

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

[0059] Ina possible implementation, the first configuration information includes names of the plurality of clusters entered by the tenant.

[0060] For example, the cloud management platform may receive the first configuration information from the tenant. It is assumed that, a name of one cluster may be denoted as a cluster #1, a name of another cluster may be denoted as a cluster #2, and a name of still another cluster may be denoted as a cluster #3 or the like.

[0061] 320: Create the cluster group based on the first configuration information, where the cluster group includes the plurality of clusters.

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

[0063] 330: Receive second configuration information from thetenant, where the second configuration information indicates to create a gateway in the cluster group.

[0064] For example, the cloud management platform may receive the second configuration information from the tenant.

[0065] 340: Create the gateway in the cluster group based on the second configuration information.

[0066] For example, the cloud management platform may create the gateway in the cluster group based on the second configuration information.

[0067] In this application, for example, an advanced traffic governance policy may be configured on the gateway.

[0068] 350: Receive third configuration information from the tenant.

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

[0070] In this application, the cluster information may determine the cluster. In other words, the cluster may be determined based on the cluster information.

[0071] For example, the cluster information may include: a name of the cluster, a name of the worker node in the cluster, and a name of the pod on the worker node.

[0072] In this application, for example, the access address corresponding to the service may be a domain name corresponding to the service. For another example, the access address corresponding to the service may be a uniform resource locator URL corresponding to the service. For still another example, the access address corresponding to the service may be an Internet Protocol IP address corresponding to the service.

[0073] The following separately describes the mapping relationships included in the third configuration information.

[0074] Forexample, the tenant may enter the service name corresponding to the service included in each K8s cluster and the access address corresponding to the service. For example, the tenant deploys two K8s clusters: a K8s cluster #1 and a K8s cluster #2. The K8s cluster #1 includes two services, which are denoted as a service #A and a service #B. The K8s cluster #2 includes one service, which is denoted as a service #C. An example is that the access address is a domain name. It is assumed that a domain name of the service #A is a domain name #1, a domain name of the service #B is a domain name #2, and a domain name of the service #C is a domain name #3. An example is that the access address is a URL. It is assumed that a URL of the service #A is a URL#1, a URL of the service #B is a URL#2,and a URL of the service #C is a URL#3. An example is that the access address is an IP address. An IP address of the service #A is an IP address #1, an IP address of the service #B is an IP address #2, and anIP address of the service #C is an IP address #3. For example, the first mapping relationship may be in a form of a table, as shown in Table 1. 7 EP 4 701 162 A1 5 10 15 20 25 30 35 40 45 50 55 Table 1 Service name Access address Service #A Domain name #1, URL #1, IP address #1 Service #B Domain name #2, URL #2, IP address #2 Service #C Domain name #3, URL #3, IP address #3

[0075] The first mapping relationship in this application may also be understood as a routing rule configured by the tenant. For example, a Hypertext Transfer Protocol (Hypertext Transfer Protocol, HTTP) route (route) represents a Layer‑7 routing rule, a Transmission Control Protocol (Transmission Control Protocol, TCP) route or a User Datagram Protocol (User Datagram Protocol, UDP) represents Layer‑4 routing rule, a Transport Layer Security Protocol (Transport Layer Security, TLS) represents a route of an encryption rule, and an HTTP2-based protocol (Google Remote Procedure Call Protocol, gRPC) released by Googlerepresents a gRPC protocol routing specification. In this application, a destination of a route is a service imported into the cluster group. As described previously, a "service" is actually provided by a pod on a specific node in a specific cluster. Therefore, a service in each cluster may be located to a specific pod that provides the service. For example, it is assumed that the service #A is provided by a pod #11 on a node (node) #1 in the K8s cluster #1, the service #B is provided by a pod #21 on a node (node) #2 in the K8s cluster #1, and the service #C is provided by a pod #31 on a node (node) #3 in the K8s cluster #2. For example, the second mapping relationship may be in a form of a table, as shown in Table 2. Table 2 Service name Access address Service #A K8s cluster #1-Node (node) #1-Pod #11 Service #B K8s cluster #1-Node (node) #2-Pod #21 Service #C K8s cluster #2-Node (node) #3-Pod #31

[0076] In this application, the "cluster information" may include, for example, the nameof the cluster, the name of the worker node in the cluster, and the name of the pod on the worker node. Alternatively, the "cluster information" may include the name of the cluster, an address of the worker node in the cluster, and an address of the pod on the worker node. Alternatively, the second mapping relationship may be understood as learning, through the second mapping relationship, that a specific service is specifically provided by a specific pod on a specific node in a specific cluster. It should be noted that a plurality of pods may provide a same service. For example, the service #A may be provided by the pod #11 and a pod #12 on the node #1.

[0077] It should be noted that, in this application, each cluster has a corresponding application gateway, and the application gateway provides routes for service access requests of a client in the corresponding cluster. For example, it is assumed that an application gateway corresponding to the K8s cluster #1 is an application gateway#1, an application gateway corresponding to the K8s cluster #2 is an application gateway #2, and an application gateway corresponding to a K8s cluster #3 is an application gateway #3. For example, the third mapping relationship may be in a form of a table, as shown in Table 3 below. Table 3 Cluster Application gateway K8s cluster #1 Application gateway #1 K8s cluster #2 Application gateway #2 K8s cluster #3 Application gateway #3

[0078] It may also be understood that an address of the application gateway corresponding to each K8s cluster may be obtained based on the third mapping relationship.

[0079] 360: Configure the third configuration information to the gateway, where the gateway is configured to send the third configuration information to the application gateway corresponding to each cluster, and the application gateway is configured to perform service access based on a request message of the client and the third configuration information.

[0080] For example, the gateway maydeliver, based on triggering of a service access request message of a client in a 8 EP 4 701 162 A1 5 10 15 20 25 30 35 40 45 50 55 specific cluster in the cluster group, the third configuration information to the application gateway corresponding to each cluster.

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

[0082] In another possible implementation, the gateway may determine, based on a service access request message of a client, configuration information that needs to be delivered and application gateways to which the required configuration information needs to be delivered. For example, if the gateway determines, based on a service access request message of a client, that the service access request is a request of the client in the cluster #1 to access the service #C in the cluster #2, the gateway may send configuration information #1 related to the service #C to onlythe application gateway #1 corresponding to the cluster #1 and the application gateway #2 corresponding to the cluster #2, where the configuration information #1 is partial configuration information in the third configuration information.

[0083] It should be noted that a global controller and various local controllers are further configured in this application. The global controller is connected to the gateway, and when the tenant uses a service of a cluster for access, the third configuration information is distributed to each local controller. The local controller may manage a cluster nearby. One local controller manages one or more sites. The local controller receives the configuration information from the global controller, and delivers the configuration information to the corresponding cluster and the corresponding application gateway.

[0084] In the method 300, mainly a process of configuration performed by the tenant is described. The process of configuration performed by thetenant may alternatively be understood with reference to FIG. 4. As shown in FIG. 4, the method includes the following steps.

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

[0086] For example, a clusterset representing a cluster group may be created, and a K8s cluster #1 and a K8s cluster #2 deployed by a tenant are added to the cluster group.

[0087] Step 2: Import a service in each K8s cluster into the cluster group.

[0088] For example, the service included in each K8s cluster may first be exported (service export), and then the service is imported (service import) into the cluster group. For example, a service #A and a service #B in the cluster #1 may be separately exported from their respective clusters, and then imported into the cluster group.

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

[0090] Step 4: Configure the gateway.

[0091] As described previously, the first mapping relationship, the second mapping relationship, and the third mapping relationship may be configured onthe gateway. Specifically, for specific content of the first mapping relationship to the third mapping relationship, refer to the description in step 350 in the method 300. Details are not described again.

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

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

[0094] In the method 300, the process of configuration performed by the tenant is described. The following begins to describe how to implement cross-cluster service access based on the configuration performed by the tenant.

[0095] In this application, an extended component is deployed in each K8s cluster. The extended component isconfigured to perform domain name resolution, and a fourth mapping relationship between the domain name and the IP address is configured on the extended component. For example, the extended component may be "operator".

[0096] It is assumed that a client #1 (an example of a first client) in a K8s cluster #1 needs to access a service #C. In this case, the client #1 may first send a request message #1 (an example of a third request message) to the extended component. The request message #1 carries a domain name (an example of a first domain name) of the service #C, and the request message #1 is used to request to obtain an IP address corresponding to the service #C. After receiving the request message, the extended component determines, based on the configured fourth mapping relationship, that the IP address corresponding to the service #C is an IP address #1, and sends a response message #1 (an example of a first response message) to the client #1. The response message #1 carries the IPaddress #1 corresponding to the service #C.

[0097] For example, after obtaining the IP address corresponding to the service #C, the client #1 sends a request message #2 (an example of a first request message) to an application gateway #1. The request message #2 carries the IP address #1, and the request message #2 is used to request to access this IP address. A first application gateway #1 determines, based on the received request message #2, that an identifier of a service corresponding to the IP address #1 is the service #C, configuration information #1 (for example, including the first mapping relationship, the second mapping relationship, and the third mapping relationship) received from the gateway, and the first mapping relationship; and determines, based on the second mapping relationship, that the service #C is located in a K8s cluster #2; and determines, based on the third mapping relationship, that the K8s cluster #2 is associated with an application gateway #2 (an example ofthe second application gateway). Therefore, the application gateway #1 may send the request message #2 to the application gateway #2. The application gateway #2 determines, based on the IP address #1 carried in the request message #2 and the first mapping relationship, that the service corresponding to the IP address is the service #C; and 9 EP 4 701 162 A1 5 10 15 20 25 30 35 40 45 50 55 determines, based on the second mapping relationship, that the service #C is provided by a pod #7 (a second pod) on a node (node) #4 (an example of a second worker node) in the cluster #2. Therefore, the application gateway #2 sends a request message #3 (an example of a second request message) to the pod #7 to request to access the service #C.

[0098] FIG. 5 is a diagram of service access performed by a client. As shown in FIG. 5, a client in a K8s cluster #1 sends a request message to an application gateway #2 through an application gateway #1, and the application gateway #2 routes the request messageto a corresponding pod, to implement cross-cluster service access. It can be learned from FIG. 5 that, in the cross-K8s cluster service access method provided in this application, service access requests may be forwarded in a uniform manner to an application gateway (for example, the application gateway #1) corresponding to the K8s cluster, and the application gateway may perform load balancing or governance. In this application, the application gateway may provide, based on a received service access request, an IP address of a pod that is to be accessed and is used to provide a target service, encapsulate the service access request message (for example, by using a virtual extensible local area network (virtual eXtensible local area network, VXLAN)), and then send the encapsulated service access request message to an application gateway (for example, the application gateway #2) corresponding to a K8s cluster in which the target service is located. The application gateway performsrouting only but does not perform load balancing. It may also be understood that load balancing needs to be performed only once on a data plane, to avoid a problem of a load imbalance caused by a plurality of times of load balancing.

[0099] It can be learned from the foregoing description that, in this application, two functions are newly extended in each tenant K8s cluster, and one of the newly added functions is that a service access request of the client may be forwarded to the application gateway corresponding to the cluster. For example, this function may be implemented through an agent component in the K8s cluster. As shown in FIG. 6, the agent component may be a route agent (route agent) component in the figure. The route agent may also monitor a service and a pod of another K8s cluster, and forward a service access request to the application gateway. For another example, this function may be implemented through a standard application programming interface API of the K8scluster. For example, no additional agent component needs to be deployed to implement this function for a specific K8s cluster as long as the API is implemented by the specific K8s cluster. Customized resource definitions (custom resource definitions, CRDs) of the API are as follows: "destinations" represents a destination network segment list; and "next-hop" represents next-hop information. These may all be understood as attributes included in a route forwarding CRD. The other new function is that automatic service discovery and automatic domain name resolution are implemented. In this application, the services for cross-cluster access need to be automatically injected into the K8s clusters of the tenant, to implement automatic service access. For example, this function may be implemented through the extended component. For another example, a service domain name of another site may be resolved through an agent component. As shown in FIG. 7, the agent component may be a domain namesystem (domain name system, DNS) agent in FIG. 7.

[0100] For example, the application gateways in this application may be gateways in a centralized manner, for example, may be deployed in advance. For example, the application gateway may be deployed in a virtual private cloud (virtual private cloud, VPC) in the cloud, or may be deployed in a conventional data center, or may be deployed in a VPC in the cloud service system. For example, the K8s cluster of the tenant may also be deployed in the VPC. Automatic network connection between the VPC where the application gateway resides and the VPC where the K8s of the tenant resides is implemented. The local controller implements PVC network connection. For another example, the application gateway may be deployed in a conventional data center, and the K8s cluster of the tenant may also be deployed in the conventional data center. Connection between a network of the application gateway and a K8s network of the tenant may be implemented throughphysical network pre-configuration.

[0101] After the application gateways are deployed, the application gateways may be managed through a control plane. Each resource pool has a corresponding application gateway. After the application gateways are deployed in a centralized manner and the tenant K8s clusters in the resource pools are added to the cluster group, the control plane performs scheduling. For example, the mapping relationship between the cluster and the application gateway may be configured. Then, cross-cluster service access requests in the tenant K8s cluster may be forwarded to a corresponding application gateway in a uniform manner.

[0102] According to the foregoing description, FIG. 8A and FIG. 8B are diagrams of a system architecture to which this application is applicable. As shown in FIG. 8A and FIG. 8B, the system architecture is sequentially divided into an orchestration layer, a global control layer, a local control layer, and a data plane forwarding layer from topto bottom. The orchestration layer provides a service-oriented console for a tenant to use automatic service discovery and automatic network interconnection functions during cross-K8s cluster service access. For example, the orchestration layer may be used for cluster group creation, service management, service gateway management, gray release, service traffic governance, service security, site management, and gateway management. The "global control layer", also referred to as a "global controller", distributes the tenant’s configurations to local controllers when the tenant uses a cross-K8s cluster service. For example, the global controller may 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" may also be referred to as a "local controller" that may manage a K8s cluster in a site nearby. One 10 EP 4 701 162 A1 5 10 15 20 25 30 35 4045 50 55 local controller may manage one or more sites. The local controller receives configurations from the global controller, and delivers configuration information to the K8s cluster and an application gateway. In this application, the global control layer and the local control layer may separately perform management and control. The global control layer logically performs unified management. The local control layer performs management and control nearby, and is partially autonomous and highly reliable. The local control layer can be interconnected to the control plane of the tenant K8s and interconnected to the application gateway, thereby implementing connection to a data plane. The "data plane forwarding layer" is used to receive configurations of the local controller. It is responsible for forwarding service access requests across the K8s cluster, and includes traffic load balancing and other governance functions.

[0103] As described previously, in this application, a pod is anentity that provides a service. After a service access request is load-balanced by an application gateway, the service access request is finally forwarded to a pod. The pod may be elastically scaled, and the application gateway needs to be notified of a pod change (for example, a location of the pod has changed or a new pod is added), so that the application gateway correctly forwards the service access request to the pod. The pod is managed by the tenant K8s cluster, and the extended component (for example, operator) in the tenant K8s needs to reversely notify the local controller. The local controller then delivers routing information of the pod to the local application gateway to update the routing information, and notifies the global controller. The global controller sends the routing information to local controllers to which other clusters in the cluster group belong. Then the local controller indicates the application gateway to deliver the routing information of the pod.

[0104] Based on the foregoing solution, in this application, the tenant configures the created cluster group, and the gateway may send the third configuration information to each application gateway, so that when receiving the service access requestof the client in the first cluster, the first application gateway may directly forward, based on the obtained third configuration information, the service access request to an application gateway corresponding to another cluster, thereby ensuring that the tenant can access a service in the another cluster. In this application, automatic service access between different clusters can be implemented, that is, automatic network connection between the clusters is implemented. In comparison with a manner in which a tenant statically and manually configures a network, this manner is more convenient, improves service experience of a user, and avoids using a sidecar to implement cross-cluster service access, thereby facilitating management and reducingmanagement costs.

[0105] It may be understood that, the term "and / or" in this specification merely describes an association relationship between associated objects, and indicates that three relationships may exist. For example, A and / or B may indicate the following cases: Only A exists, both A and B exist, and only B exists. In addition, the character " / " in this specification generally indicates an "or" relationship between the associated objects.

[0106] A person skilled in the art may be aware that, with reference to the examples described in embodiments disclosed in this specification, units and algorithm steps can be implemented by hardware or a combination of computer software and hardware in this application. Whether a function is performed by hardware or hardware driven by computer software depends on particular applications and design constraints of the technical solutions. A person skilled in the art may use different methods to implement the described functions for eachparticular application, but it should not be considered that the implementation goes beyond the scope of this application.

[0107] In embodiments of this application, the apparatus may be divided into functional modules based on the foregoing method examples. For example, each functional module may be obtained through division based on each corresponding function, or two or more functions may be integrated into one processing module. The integrated module may be implemented in a form of hardware, or may be implemented in a form of a software functional module. It should be noted that, in embodiments of this application, module division is an example, and is merely a logical function division. During actual implementation, another division manner may be used. An example in which each functional module is obtained through division based on each corresponding function is used below for description.

[0108] FIG. 9 is a block diagram of an apparatus 900 according to an embodiment of thisapplication. As shown in the figure, theapparatus 900 may include a transceiver module 910 and a processing module 920.

[0109] The modules are separately configured to perform steps of the foregoing method. Details are not described herein again.

[0110] It should be further understood that the apparatus 900 herein is embodied in a form of functional units. The term "unit" herein may be an application-specific integrated circuit (application-specific integrated circuit, ASIC), an electronic circuit, a processor (for example, a shared processor, a dedicated processor, or a group processor) configured to execute one or more software or firmware programs, a memory, a merged logic circuit, and / or another appropriate component that supports the described function.

[0111] The apparatus 900 in each of the foregoing solutions has a function of implementing corresponding steps in the method 300. The function may be implemented by hardware, or may be implemented by hardware executing correspond-ing software. The hardware or software includes one or more modules corresponding to the foregoing functions. For example, the transceiver module may be replaced with a processor, to separately perform receiving and sending operations and related processing operations in the method embodiments. In addition, the processing module may be a processing circuit. 11 EP 4 701 162 A1 5 10 15 20 25 30 35 40 45 50 55

[0112] In a possible implementation, the apparatus 900 may be an apparatus that is in the method 300 and that is applied to a cloud management platform, and the apparatus is configured to perform actions in the method 300.

[0113] In another possible implementation, the apparatus 900 may be a cloud management platform in the method 300, where the cloud management platform is configured to perform actions in the method 300.

[0114] It should be noted that the apparatus in FIG. 9 may be the cloud management platform (or an apparatus in the cloud management platform) in the foregoingmethod embodiments, or may be a chip or a chip system corresponding to the cloud management platform (or an apparatus in the cloud management platform), for example, a system on chip (system on chip, SoC). The processing module is a processor, a microprocessor, or an integrated circuit integrated on the chip. This is not limited herein.

[0115] FIG. 10 is a block diagram of another apparatus 1000 according to an embodiment of this application. As shown in the figure, the apparatus 1000 includes at least one processor 1020. The processor 1020 is coupled to a memory, and is configured to execute instructions stored in the memory, to transmit a signal and / or receive a signal. Optionally, the apparatus 1000 further includes the memory 1030, configured to store the instructions. Optionally, the apparatus 1000 further includes a transceiver 1010, and the processor 1020 controls the transceiver 1010 to send a signal and / or receive a signal.

[0116] It should be understood that the processor1020 and the memory 1030 may be integrated into one processing apparatus, and the processor 1020 is configured to execute program code stored in the memory 1030 to implement the foregoing functions. During specific implementation, the memory 1030 may alternatively be integrated into the processor 1020, or may be independent of the processor 1020.

[0117] It should be further understood that the transceiver 1010 may include a receiver (or referred to as a receiving machine) and a transmitter (or referred to as a transmitting machine). The transceiver may further include an antenna, and there may be one or more antennas. The transceiver 1010 may alternatively be a communication interface or an interface circuit.

[0118] 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 transceiver module 910 in the apparatus 900.

[0119] In a solution, the apparatus 1000 isconfigured to implement steps corresponding to an apparatus that is in the embodiment of the method 300 and that is applied to the cloud management platform. In another solution, the apparatus 1000 is configured to implement steps corresponding to the cloud management platform in the embodiment of the method 300.

[0120] For example, the processor 1020 is configured to execute a computer program or instructions stored in the memory 1030, to implement the steps in the method 300.

[0121] FIG. 11 is a diagram of an architecture of a computing apparatus cluster according to an embodiment of this application. The computing apparatus cluster includes at least one computing apparatus. The computing apparatus may be a server, for example, a central server, an edge server, or a local server in a local data center. In some embodiments, the computing apparatus may alternatively be a terminal apparatus, for example, a desktop computer, a notebook computer, or a smartphone. As shown in FIG. 11, thecomputing apparatus cluster includes at least one computing apparatus 1100. Memories 1130 in the one or more computing apparatuses 1100 in the computing apparatus cluster may store same instructions used for performing actions that are performed by the cloud management platform (or an apparatus in the cloud management platform) in the method 300.

[0122] In some possible implementations, alternatively, the memories 1130 in the one or more computing apparatuses 1100 in the computing apparatus cluster may separately store some of the instructions used for performing the actions that are performed by the cloud management platform (or an apparatus in the cloud management platform) in the method 300 described in the foregoing embodiment. In other words, a combination of one or more computing apparatuses 1100 may collectively execute the instructions used for performing the actions that are performed by the cloud management platform (or an apparatus in the cloud management platform) describedin the foregoing embodiment.

[0123] It should be noted that the memories 1130 in different computing apparatuses 1100 in the computing apparatus cluster may store different instructions, which are separately used to perform some functions of the computing apparatus 1100. In other words, the instructions stored in the memories 1130 in different computing apparatuses 1100 may implement functions of one or more of the transceiver module 910 and the processing module 920.

[0124] Alternatively, the memories 1130 in different computing apparatuses 1100 in the computing apparatus cluster may store different instructions, which are separately used to perform some functions of the cloud management platform (or an apparatus in the cloud management platform) corresponding to the apparatus 900 or the apparatus 1000. In other words, the instructions stored in the memories 1130 in different computing apparatuses 1100 may implement functions of one or more of the transceiver module 910 and theprocessing module 920.

[0125] In some possible implementations, the one or more computing apparatuses in the computing apparatus cluster may be connected through a network. The network may be a wide area network, a local area network, or the like. FIG. 12 shows a possible implementation. As shown in FIG. 12, two computing apparatuses 1200A and 1200B are connected 12 EP 4 701 162 A1 5 10 15 20 25 30 35 40 45 50 55 through a network. Specifically, each computing apparatus is connected to the network via a communication interface in the computing apparatus.

[0126] It should be understood that functions of the computing apparatus 1200A shown in FIG. 12 may alternatively be completed by a plurality of computing apparatuses 1100. Similarly, functions of the computing apparatus 1200B may alternatively be implemented by a plurality of computing apparatuses 1100.

[0127] An embodiment further provides a computer program product including instructions. The computer program product may be softwareor a program product that includes the instructions and can be run on a computing apparatus cluster or can be stored in any usable medium. When the computer program product is run by the computing apparatus cluster, the computing apparatus cluster is enabled to perform the foregoing method, or the computing apparatus cluster is enabled to implement functions of the foregoing apparatus.

[0128] An embodiment further provides a computer-readable storage medium. The computer-readable storage medium may be any usable medium that can be stored by a computing apparatus, or a data storage apparatus including one or more usable media, for example, a data center. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, ora magnetic tape), an optical medium (forexample, adigital video disc (digital video disc, DVD)), a semiconductor medium (for example, a solid-state drive), or the like. The computer-readable storage medium includes instructions. When the instructionsin the computer-readable storage medium are executed on the computing apparatus, the computing apparatus is enabled to perform the foregoing method.

[0129] An embodiment further provides a computer-readable storage medium. The computer-readable storage medium may be any usable medium that can be stored by a computing apparatus, or a data storage apparatus including one or more usable media, for example, a data center. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk drive, or a magnetic tape), an optical medium (for example, a DVD), a semiconductor medium (for example, a solid-state drive), or the like. The computer-readable storage medium includes instructions. When the instructions in the computer-readable storage medium are executed by a computing apparatus cluster, the computing apparatus cluster is enabled to perform the foregoing method.

[0130] A person of ordinary skill in the art may be aware that, in combination with the examples described inembodiments disclosed in this specification, units and algorithm steps may be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether the functions are performed by hardware or software depends on particular applications and design constraints of the technical solutions. A person skilled in the art may use different methods to implement the described functions for each particular application, but it should not be considered that the implementation goes beyond the scope of this application.

[0131] It may be clearly understood by a person skilled in the art that, for the purpose of convenient and brief description, for a detailed working process of the foregoing system, apparatus, and unit, reference may be made to a corresponding process in the foregoing method embodiments. Details are not described herein again.

[0132] In the several embodiments provided in this application, it should be understood that the disclosed system, apparatus,and method may be implemented in other manners. For example, the described apparatus embodiments are merely examples. For example, division into the units is merely logical function division and there may be another division manner during actual implementation. For example, a plurality of units or components may be combined or integrated into another system, or some features may be ignored or not performed. In addition, the displayed or discussed mutual couplings or direct couplings or communication connections may be implemented by using some interfaces. The indirect couplings or communication connections between the apparatuses or units may be implemented electronically, me- chanically, or in other forms.

[0133] The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one position, or may be distributed on a plurality of network units. Some or all of the units may be selected based onactual requirements to achieve the objectives of the solutions of embodiments.

[0134] In addition, functional units in embodiments of this application may be integrated into one processing unit, each of the units may exist alone physically, or two or more units may be integrated into one unit.

[0135] When the functions are implemented in the form of a software functional unit and sold or used as an independent product, the functions may be stored in a computer-readable storage medium. Based on such an understanding, the technical solutions of this application essentially, or the part contributing to the conventional technology, or some of the technical solutions may be implemented in a form of a software product. The computer software product is stored in a storage medium and includes a plurality of instructions for instructing a computer apparatus (which may be a personal computer, a server, a network apparatus, or the like) to perform all or some of the steps of the method describedin embodiments of this application. The foregoing storage medium includes any medium that can store program code, such as a USB flash drive, a removable hard disk, a read-only memory (read-only memory, ROM), a random access memory (random access memory, RAM), a magnetic disk, or an optical disc.

[0136] The foregoing descriptions are merely specific implementations of this application, but are not intended to limit the protection scope of this application. Any variation or replacement readily figured out by a person skilled in the art within the technical scope disclosed in this application shall fall within the protection scope of this application. Therefore, the 13 EP 4 701 162 A1 5 10 15 20 25 30 35 40 45 50 55 protection scope of this application shall be subject to the protection scope of the claims. Claims 1. A method for cross-cluster service access, wherein the method is applied to a cloud management platform in a cloud service system, the cloud service system comprises aplurality of clusters, each cluster at least comprises a client and at least one worker node, each worker node comprises at least one pod, each pod is configured to provide a service, and the method comprises: receiving first configuration information from a tenant, wherein the first configuration information indicates to create a cluster group for the plurality of clusters; creating the cluster group based on the first configuration information, wherein the cluster group comprises the plurality of clusters; receiving second configuration information from the tenant, wherein the second configuration information indicates to create a gateway in the cluster group; creating the gateway in the cluster group based on the second configuration information; receiving third configuration information from the tenant, wherein the third configuration information comprises: a first mapping relationship between a service name corresponding to a service comprised in each cluster and a correspondingaccess address, a second mapping relationship between the service name corresponding to the service comprised 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 determines the cluster; and configuring the third configuration information to the gateway, wherein the gateway is configured to send the third configuration information to the application gateway corresponding to eachcluster, and the application gateway is configured to perform service access based on a request message of the client and the third configuration information. 2. The method according to claim 1, wherein the access address corresponding to the service comprises 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. Themethod according to claim 1 or 2, wherein the cluster information comprises: a name of the cluster, a name of the worker node in the cluster, and a name of the pod on the worker node. 4. The method according to any one of claims 1 to 3, wherein the plurality of clusters comprise a first cluster and a second cluster, the first cluster comprises a first client, the first cluster is associated with a first application gateway, and the method further comprises: obtaining, by the first client, a first IP address corresponding to a first domain name; sending, by the first client, a first request message to the first application gateway, wherein the first request message carries the first IP address, and the first request message is used to request to access the first IP address; determining, by the first application gateway based on the first request message and the first mapping relation- ship, that a service identifier corresponding to the first IP address is a first identifier,determining, based on the second mapping relationship, that the first identifier is an identifier corresponding to a service in the second cluster, and determining, based on the third mapping relationship, that the second cluster is associated with a second application gateway; and sending, by the first application gateway, the first request message to the second application gateway. 5. The method according to claim 4, wherein the method further comprises: sending, by the gateway, the third configuration information to the first application gateway and the second application gateway. 6. The method according to claim 5, wherein the method further comprises: determining, by the second application gateway based on 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 14 EP 4 701 162 A1 5 10 15 20 25 30 35 40 45 50 55 identifier, and determining, based on the secondmapping relationship, that the first identifier corresponds to a second pod in a second worker node in the second cluster; and sending, by the second application gateway, a second request message to the second pod, wherein the second request message is used to request to access the service corresponding to the first identifier. 7. The method according to any one of claims 4 to 6, wherein the first cluster further comprises a first module, a fourth mapping relationship between the domain name and the IP address is configured on the first module, and the first module is configured to perform domain name resolution; and obtaining, by the first client, the first IP address corresponding to the first domain name comprises: sending, by the first client, a third request message to the first module, wherein the third request message carries the 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;and receiving, by the first client, a first response message from the first module, wherein the first response message carries the first IP address, and the first IP address is determined by the first module. 8. An apparatus, wherein the apparatus is applied to a cloud management platform in a cloud service system, the cloud service system comprises a plurality of clusters, each cluster at least comprises a client and at least one worker node, each worker node comprises at least one pod, each pod is configured to provide a service, and the apparatus comprises a transceiver module and a processing module; the transceiver module is configured to receive first configuration information from a tenant, wherein the first configuration information indicates to create a cluster group for the plurality of clusters; the processing module is configured to create the cluster group based on the first configuration information, wherein the cluster group comprises the plurality of clusters; thetransceiver module is configured to receive second configuration information from the tenant, wherein the second configuration information indicates to create a gateway in the cluster group; the processing module is configured to create the gateway in the cluster group based on the second configuration information; the transceiver module is configured to receive third configuration information from the tenant, wherein the third configuration information comprises: a first mapping relationship between a service name corresponding to a service comprised in each cluster and a corresponding access address, a second mapping relationship between the service name corresponding to the service comprised 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 determines the cluster; and the processing module is configured to configure the thirdconfiguration information to the gateway, wherein the gateway is configured to send the third configuration information to the application gateway corresponding to each cluster, and the application gateway is configured to perform service access based on a request message of the client and the third configuration information. 9. The apparatus according to claim 8, wherein the access address corresponding to the service comprises 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. 10. The apparatus according to claim 8 or 9, wherein the cluster information comprises: a name of the cluster, a name of the worker node in the cluster, and a name of the pod on the worker node. 11. The apparatus according to any one of claims 8 to 10, wherein the plurality of clusters comprise a first cluster and a second cluster, the first cluster comprises afirst client, and the first cluster is associated with a first application gateway; the first client is configured to obtain a first IP address corresponding to a first domain name; the first client is configured to send a first request message to the first application gateway, wherein the first request message carries the first IP address, and the first request message is used to request to access the first IP address; the first application gateway is configured to: determine, based on the first request message and the first mapping relationship, that a service identifier corresponding to the first IP address is a first identifier, determine, based on the second mapping relationship, that the first identifier is an identifier corresponding to a service in the second 15 EP 4 701 162 A1 5 10 15 20 25 30 35 40 45 50 55 cluster, and determine, based on the third mapping relationship, that the second cluster is associated with a second application gateway; and the first application gatewayis configured to send the first request message to the second application gateway. 12. The apparatus according to claim 11, wherein the gateway is configured to send the third configuration information to the first application gateway and the second application gateway. 13. The apparatus according to claim 12, wherein the second application gateway is configured to: determine, based on 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 determine, based on the second mapping relationship, that the first identifier corresponds to a second pod in a second worker node in the second cluster; and the second application gateway is configured to send a second request message to the second pod, wherein the second request message is used to request to access the service corresponding to the first identifier. 14. The apparatus according to any one of claims 11to 13, wherein the first cluster further comprises a first module, a fourth mapping relationship between the domain name and the IP address is configured on the first module, and the first module is configured to perform domain name resolution; and that the first client is configured to obtain the first IP address corresponding to the first domain name comprises: the first client is configured to send a third request message to the first module, wherein the third request message carries the 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; and the first client is configured to receive a first response message from the first module, wherein the first response message carries the first IP address, and the first IP address is determined by the first module. 15. A computing apparatus, comprising a processor and a memory, wherein the processor runs instructions in the memory, so that theprocessor performs the method according to any one of claims 1 to 7. 16. A computing apparatus cluster, comprising at least one computing apparatus, wherein each computing apparatus comprises a processor and a memory; and the processor of the at least one computing apparatus is configured to execute instructions stored in the memory of the at least one computing apparatus, so that the computing apparatus cluster performs the method according to any one of claims 1 to 7. 17. A computer program product comprising instructions, wherein when the instructions are run by acomputing apparatus cluster, the computing apparatus cluster is enabled to perform the method according to any one of claims 1 to 7. 18. A computer-readable storage medium, comprising computer program instructions, wherein when the computer program instructions are executed by a computing apparatus cluster, the computing apparatus cluster performs the method according to any one of claims 1 to 7. 16 EP 4 701 162 A1 5 10 1520 25 30 35 40 45 50 55 17 EP 4 701 162 A1 18 EP 4 701 162 A1 19 EP 4 701 162 A1 20 EP 4 701 162 A1 21 EP 4 701 162 A1 22 EP 4 701 162 A1 23 EP 4 701 162 A1 24 EP 4 701 162 A1 25 EP 4 701 162 A1 26 EP 4 701 162 A1 27 EP 4 701 162 A1 28 EP 4 701 162 A1 5 10 15 20 25 30 35 40 45 50 55 29 EP 4 701 162 A1 5 10 15 20 25 30 35 40 45 50 55 30 EP 4 701 162 A1 REFERENCES CITED IN THE DESCRIPTION This list of references cited by the applicant is for the reader’s convenience only. It does not form part of the European patent document. Even though great care has been taken in compiling the references, errors or omissions cannot be excluded and the EPO disclaims all liability in this regard. Patent documents cited in the description • CN 202310539823

[0001] • CN 202311324854

[0002]

Claims

1. A method for cross-cluster service access, wherein the method is applied to a cloud management platform in a cloud service system, the cloud service system comprises a plurality of clusters, each cluster at least comprises a client and at least one worker node, each worker node comprises at least one pod, each pod is configured to provide a service, and the method comprises: receiving first configuration information from a tenant, wherein the first configuration information indicates to create a cluster group for the plurality of clusters; creating the cluster group based on the first configuration information, wherein the cluster group comprises the plurality of clusters; receiving second configuration information from the tenant, wherein the second configuration information indicates to create a gateway in the cluster group; creating the gateway in the cluster group based on the second configuration information; receiving third configuration information from the tenant, wherein the third configuration information comprises: a first mapping relationship between a service name corresponding to a service comprised in each cluster and a corresponding access address, a second mapping relationship between the service name corresponding to the service comprised 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 determines the cluster; and configuring the third configuration information to the gateway, wherein the gateway is configured to send the third configuration information to the application gateway corresponding to each cluster, and the application gateway is configured to perform service access based on a request message of the client and the third configuration information.

2. The method according to claim 1, wherein the access address corresponding to the service comprises 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, wherein the cluster information comprises: a name of the cluster, a name of the worker node in the cluster, and a name of the pod on the worker node.

4. The method according to any one of claims 1 to 3, wherein the plurality of clusters comprise a first cluster and a second cluster, the first cluster comprises a first client, the first cluster is associated with a first application gateway, and the method further comprises: obtaining, by the first client, a first IP address corresponding to a first domain name; sending, by the first client, a first request message to the first application gateway, wherein the first request message carries the first IP address, and the first request message is used to request to access the first IP address; determining, by the first application gateway based on the first request message and the first mapping relationship, that a service identifier corresponding to the first IP address is a first identifier, determining, based on the second mapping relationship, that the first identifier is an identifier corresponding to a service in the second cluster, and determining, based on the third mapping relationship, that the second cluster is associated with a second application gateway; and sending, by the first application gateway, the first request message to the second application gateway.

5. The method according to claim 4, wherein the method further comprises: sending, by the gateway, the third configuration information to the first application gateway and the second application gateway.

6. The method according to claim 5, wherein the method further comprises: determining, by the second application gateway based on 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 determining, based on the second mapping relationship, that the first identifier corresponds to a second pod in a second worker node in the second cluster; and sending, by the second application gateway, a second request message to the second pod, wherein the second request message is used to request to access the service corresponding to the first identifier.

7. The method according to any one of claims 4 to 6, wherein the first cluster further comprises a first module, a fourth mapping relationship between the domain name and the IP address is configured on the first module, and the first module is configured to perform domain name resolution; and obtaining, by the first client, the first IP address corresponding to the first domain name comprises: sending, by the first client, a third request message to the first module, wherein the third request message carries the 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; and receiving, by the first client, a first response message from the first module, wherein the first response message carries the first IP address, and the first IP address is determined by the first module.

8. An apparatus, wherein the apparatus is applied to a cloud management platform in a cloud service system, the cloud service system comprises a plurality of clusters, each cluster at least comprises a client and at least one worker node, each worker node comprises at least one pod, each pod is configured to provide a service, and the apparatus comprises a transceiver module and a processing module; the transceiver module is configured to receive first configuration information from a tenant, wherein the first configuration information indicates to create a cluster group for the plurality of clusters; the processing module is configured to create the cluster group based on the first configuration information, wherein the cluster group comprises the plurality of clusters; the transceiver module is configured to receive second configuration information from the tenant, wherein the second configuration information indicates to create a gateway in the cluster group; the processing module is configured to create the gateway in the cluster group based on the second configuration information; the transceiver module is configured to receive third configuration information from the tenant, wherein the third configuration information comprises: a first mapping relationship between a service name corresponding to a service comprised in each cluster and a corresponding access address, a second mapping relationship between the service name corresponding to the service comprised 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 determines the cluster; and the processing module is configured to configure the third configuration information to the gateway, wherein the gateway is configured to send the third configuration information to the application gateway corresponding to each cluster, and the application gateway is configured to perform service access based on a request message of the client and the third configuration information.

9. The apparatus according to claim 8, wherein the access address corresponding to the service comprises 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.

10. The apparatus according to claim 8 or 9, wherein the cluster information comprises: a name of the cluster, a name of the worker node in the cluster, and a name of the pod on the worker node.

11. The apparatus according to any one of claims 8 to 10, wherein the plurality of clusters comprise a first cluster and a second cluster, the first cluster comprises a first client, and the first cluster is associated with a first application gateway; the first client is configured to obtain a first IP address corresponding to a first domain name; the first client is configured to send a first request message to the first application gateway, wherein the first request message carries the first IP address, and the first request message is used to request to access the first IP address; the first application gateway is configured to: determine, based on the first request message and the first mapping relationship, that a service identifier corresponding to the first IP address is a first identifier, determine, based on the second mapping relationship, that the first identifier is an identifier corresponding to a service in the second cluster, and determine, based on the third mapping relationship, that the second cluster is associated with a second application gateway; and the first application gateway is configured to send the first request message to the second application gateway.

12. The apparatus according to claim 11, wherein the gateway is configured to send the third configuration information to the first application gateway and the second application gateway.

13. The apparatus according to claim 12, wherein the second application gateway is configured to: determine, based on 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 determine, based on the second mapping relationship, that the first identifier corresponds to a second pod in a second worker node in the second cluster; and the second application gateway is configured to send a second request message to the second pod, wherein the second request message is used to request to access the service corresponding to the first identifier.

14. The apparatus according to any one of claims 11 to 13, wherein the first cluster further comprises a first module, a fourth mapping relationship between the domain name and the IP address is configured on the first module, and the first module is configured to perform domain name resolution; and that the first client is configured to obtain the first IP address corresponding to the first domain name comprises: the first client is configured to send a third request message to the first module, wherein the third request message carries the 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; and the first client is configured to receive a first response message from the first module, wherein the first response message carries the first IP address, and the first IP address is determined by the first module.

15. A computing apparatus, comprising 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 apparatus cluster, comprising at least one computing apparatus, wherein each computing apparatus comprises a processor and a memory; and the processor of the at least one computing apparatus is configured to execute instructions stored in the memory of the at least one computing apparatus, so that the computing apparatus cluster performs the method according to any one of claims 1 to 7.

17. A computer program product comprising instructions, wherein when the instructions are run by a computing apparatus cluster, the computing apparatus cluster is enabled to perform the method according to any one of claims 1 to 7.

18. A computer-readable storage medium, comprising computer program instructions, wherein when the computer program instructions are executed by a computing apparatus cluster, the computing apparatus cluster performs the method according to any one of claims 1 to 7.

Images