A cross-cluster application routing access method, system, device and medium

By setting up delegate clusters and deploying proxy components in the kubernetes system, using Nginx configuration files to achieve cross-cluster application routing access, solving the problem that native ingress resources cannot achieve cross-cluster service access, and realizing the function of accessing applications within the cluster outside the cluster.

CN115314432BActive Publication Date: 2024-12-06JINAN INSPUR DATA TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202210911494.3
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-07-30
Publication Date
2024-12-06
Estimated Expiration
2042-07-30

AI Technical Summary

Technical Problem

Existing kubernetes systems cannot achieve cross-cluster service access, and native ingress resources can only provide load balancing within the cluster, but cannot achieve external access to cross-cluster services.

Method used

By building multiple clusters, one of which is set as a delegate cluster, deploying proxy components and application routing import controllers, creating application routing export resources, and implementing application routing access across clusters based on Nginx configuration files, using delegate components and proxy components for Metadata exchange and configuration file modification enable external cluster access to applications within the cluster through preset domain names.

Benefits of technology

It realizes cross-cluster application routing access, enriches the container cloud platform functions, solves the problem that native ingress resources cannot achieve cross-cluster service access, and realizes automatic discovery and real-time forwarding of application routing in the interconnected cluster.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115314432B_ABST
    Figure CN115314432B_ABST
Patent Text Reader

Abstract

The present application discloses a cross-cluster application routing access method, system, device and medium to solve the technical problem that the prior art cannot achieve cross-cluster application access. The method includes: building several clusters; wherein, one or more of the clusters have an application program interface service API Server that can be accessed in other clusters; setting the cluster that the application program interface service API Server can access in other clusters as a delegate cluster; deploying proxy components and application routing import controllers, and creating application routing export resources; controlling the application routing import controller to listen to the application routing import resources, and modifying the application routing import controller; accessing cross-cluster applications based on preset domain names. The present application uses the above method to achieve access to services within the cluster through application routing from outside the cluster. It solves the problem that native ingress resources in the prior art cannot achieve cross-cluster service access.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a cross-cluster application routing access method, system, device and medium. Background Art

[0002] Most cloud platforms are based on the Kubernetes framework, providing users with a functional system with application management as the core. Native Kubernetes usually manages applications in clusters, and cannot provide cross-cluster application scheduling, management, and access. With the extensive use of Kubernetes, more and more users will deploy multiple Kubernetes clusters to achieve application isolation, high availability, and disaster recovery through multiple clusters. To achieve these functions, it is necessary to achieve cross-cluster service or application access.

[0003] There are many projects in the open source community to solve this problem. Typical open source projects include Submariner, Karmada, Skupper, etc. These open source projects have achieved cross-cluster application access, but they are limited to accessing applications or services in another cluster from within a cluster. For example, in Submariner, the Kubernetes service can be exported to all interconnected clusters, and this service can be accessed through ClusterIP or service name in any interconnected cluster, but access to cross-cluster services or applications from outside the cluster is not achieved.

[0004] In order to achieve external access to services within the cluster in the native kubernetes, a routing application resource ingress is provided. By creating a specific routing application resource ingress, services within the cluster can be directly accessed through the corresponding URL outside the cluster, and the load balancing function is realized. However, the native routing application resource ingress cannot achieve cross-cluster service access. Therefore, there is still a lack of a solution to achieve external access to cross-cluster internal services. Summary of the invention

[0005] The embodiments of the present application provide a cross-cluster application routing access method, system, device and medium to solve the technical problem that the prior art cannot implement cross-cluster application access.

[0006] On the one hand, an embodiment of the present application provides a cross-cluster application routing access method, the method comprising:

[0007] Building several clusters; wherein one or more of the clusters have an application program interface service APIServer that can be accessed in other clusters;

[0008] Set the cluster that the API Server can access in other clusters as a delegate cluster;

[0009] Deploy proxy components and application routing import controllers, and create application routing export resources;

[0010] Based on the application route import resource created by the proxy component, control the application route import controller to listen to the application route import resource, and modify the application route import controller;

[0011] Access cross-cluster applications based on preset domain names.

[0012] In one implementation of the present application, after setting the cluster that the application program interface service API Server can access in other clusters as a delegate cluster, the method further includes:

[0013] Deploy the delegate component;

[0014] Setting a configuration file for the delegate component;

[0015] The designated port is listened to based on the delegate component and the set configuration file.

[0016] In one implementation of the present application, the delegation component establishes connections with a plurality of interconnected clusters respectively for metadata exchange between the plurality of interconnected clusters.

[0017] In one implementation of the present application, the proxy component and the application routing import controller are deployed based on dameonset.

[0018] In one implementation of the present application, controlling the application route import controller to monitor the application route import resource specifically includes:

[0019] Parsing the backend service information corresponding to the resource imported by the application route;

[0020] Modify the Nginx configuration file based on the parsed backend service information;

[0021] Based on the modified Nginx configuration file, determine whether reloading is required;

[0022] Execute a reload to make the modified Nginx configuration file take effect.

[0023] In one implementation of the present application, modifying the Nginx configuration file based on the parsed backend service information specifically includes:

[0024] Determine whether there is a resource update situation in the application routing import resource; wherein the resource update situation includes: resource creation and resource modification;

[0025] When the application routing import resource exists and a resource is created, the domain name specified in the resource is matched with the resolved backend service one by one according to the preset rules and written into the Nginx configuration file;

[0026] When there is a resource modification in the application routing import resource, the Nginx configuration file is modified according to the content of the resource modification.

[0027] In addition, an embodiment of the present application further provides a cross-cluster application routing access system, the system comprising:

[0028] A cluster building module, used to build several clusters; wherein one or more of the several clusters have an application program interface service API Server that can be accessed in other clusters;

[0029] The delegate cluster setting module is used to set the cluster that the application program interface service API server can access in other clusters as a delegate cluster;

[0030] The component deployment module is used to deploy proxy components, application routing import controllers, application routing export controllers, and create application routing export resources;

[0031] A component control module, used to control the application route import controller to listen to the application route import resource;

[0032] The access module is used to access cross-cluster applications based on a preset domain name.

[0033] In one implementation of the present application, the component deployment module includes:

[0034] The delegate component deployment submodule is used to deploy delegate components;

[0035] A file configuration submodule, used to set a configuration file for the delegate component;

[0036] The monitoring submodule is used to monitor the designated port based on the delegation component and the set configuration file.

[0037] The embodiment of the present application also provides a cross-cluster application routing access device, the device comprising:

[0038] at least one processor; and,

[0039] a memory communicatively connected to the at least one processor; wherein,

[0040] The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to:

[0041] Building several clusters; wherein one or more of the clusters have an application program interface service APISever that can be accessed in other clusters;

[0042] Set the cluster that the API Server can access in other clusters as a delegate cluster;

[0043] Deploy proxy components and application routing import controllers, and create application routing export resources;

[0044] Based on the application route import resource created by the proxy component, control the application route import controller to listen to the application route import resource, and modify the application route import controller;

[0045] Access cross-cluster applications based on preset domain names.

[0046] The embodiment of the present application also relates to a non-volatile computer storage medium for cross-cluster application routing access, which stores computer executable instructions, and the computer executable instructions are configured as follows:

[0047] Building several clusters; wherein one or more of the clusters have an application program interface service APIServer that can be accessed in other clusters;

[0048] Set the cluster that the API Server can access in other clusters as a delegate cluster;

[0049] Deploy proxy components and application routing import controllers, and create application routing export resources;

[0050] Based on the application route import resource created by the proxy component, control the application route import controller to listen to the application route import resource, and modify the application route import controller;

[0051] Access cross-cluster applications based on preset domain names.

[0052] The embodiment of the present application provides a cross-cluster application routing access method, which enriches the functions of the container cloud platform by setting up and deploying cluster components, and realizes the automatic discovery of application routing in the interconnected cluster. The application routing import controller monitors the application routing import resources, and modifies the nginx configuration file in real time according to the creation of resources, so as to realize the forwarding of access requests through application routing in the interconnected cluster. And the configuration file is modified in real time according to the resource information, so as to realize the access to the services in the cluster through application routing from outside the cluster. It solves the problem that the native ingress resources in the existing technology cannot realize cross-cluster service access. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0054] Figure 1 A flow chart of a cross-cluster application routing access method provided in an embodiment of the present application;

[0055] Figure 2 A cross-cluster application routing access system structure diagram provided for an embodiment of the present application;

[0056] Figure 3 A schematic diagram of a cross-cluster application routing access device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0057] In order to make the purpose, technical solution and advantages of the present application clearer, the technical solution of the present application will be clearly and completely described below in combination with the specific embodiments of the present application and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present application.

[0058] The technical solution proposed in the embodiments of the present application is described in detail below with reference to the accompanying drawings.

[0059] Figure 1 A flow chart of a cross-cluster application routing access method provided in an embodiment of the present application. Figure 1 As shown, the method mainly includes the following steps:

[0060] Step 101: Build several clusters; wherein one or more of the clusters have an application program interface service API Server that can be accessed in other clusters.

[0061] In the embodiment of the present application, multiple k8s clusters are first built, and it is necessary to ensure that the cluster of the application programming interface service API Server of at least one cluster can be accessed in other clusters.

[0062] Step 102: Set the cluster that the application program interface service API Server can access in other clusters as a delegate cluster.

[0063] In the embodiment of the present application, the cluster set in step 101 that can access the application program interface service API Server in other clusters is selected as the delegate cluster broker, and the delegate component broker is deployed.

[0064] Furthermore, after the broker component is deployed, a configuration file is set for the delegate component broker, and then a specific port is specified to be listened to according to the broker component and the set configuration file.

[0065] It should be noted that the broker component is connected to multiple interconnected clusters and is responsible for exchanging metadata between multiple interconnected clusters.

[0066] Step 103: deploy the proxy component and the application routing import controller and the application routing export controller, and create the application routing export resource.

[0067] In the embodiment of the present application, the proxy component and the application routing import controller are deployed based on dameonset. Since the application in the cluster needs to be accessed through application routing outside the cluster, the application routing import controller component is required to be deployed in the form of hostnetwork, or hostPort is specified to monitor the specified port of the host machine.

[0068] Step 104: Control the application route import controller to listen to the application route import resource.

[0069] In an embodiment of the present application, when the local cluster agent component listens to the creation of an application routing export resource, it will send a creation event to the application programming interface service APIServer of the broker delegation cluster. At the same time, the agent components of other clusters will listen to the creation of a new application routing export resource ingress-export resource through the application programming interface service APIServer of the broker cluster. At this time, the agent agent component will create an application routing import resource ingress-import resource in the local cluster.

[0070] Furthermore, select a cluster to create an application routing export resource.

[0071] Furthermore, after the agent component in another cluster listens to the creation event of the above resource, it will create an ingress-import resource locally. The YAML file of the resource is basically the same as the ingress-export resource mentioned above.

[0072] In an embodiment of the present application, the application route import controller is controlled to listen to the application route import resource and first parse the corresponding backend service information in the resource of the application route import resource. Based on the parsed backend service information, the Nginx configuration file is modified. Based on the modified Nginx configuration file, it is determined whether reloading is required and reloading is performed to make the modified Nginx configuration file take effect.

[0073] After the modification is complete, execute the Nginx reload command to make the configuration take effect.

[0074] Specifically, to modify the Nginx configuration file, first determine whether there is a resource update for the application routing import resource; wherein, the resource update includes: resource creation and resource modification; when there is a resource creation for the application routing import resource, the domain name specified in the resource is matched with the resolved backend service one by one and written into the Nginx configuration file according to the preset rule; when there is a resource modification for the application routing import resource, the Nginx configuration file is modified according to the content of the resource modification. Generally speaking, for a small amount of modification, it is sufficient to modify it directly, and for modifying the rule part of the application routing export resource at the same time, the host name of the application routing export resource, the newly added path and deleted path of the application routing export resource, etc., it is also necessary to write the backend service one by one into the Nginx configuration file like when the resource is created.

[0075] Step 105: Access cross-cluster applications based on a preset domain name.

[0076] In the embodiment of the present application, after the above operations, any PC outside the cluster can access the cross-cluster internal application through the preset domain name www.test.com as long as it can connect to any node in the interconnected cluster. For example, node node1 of cluster1 in the current interconnected cluster can be connected to a PC outside the cluster with an IP of 100.2.216.244. Then modify the configuration file / etc / hosts on the PC outside the cluster and add the following content www.test.com100.2.216.244. After the modification is completed, the application in the cluster can be accessed through www.test.com / aaa.

[0077] The embodiment of the present application provides a cross-cluster application routing access method, which enriches the functions of the container cloud platform by setting up and deploying cluster components, and realizes the automatic discovery of application routing in the interconnected cluster. The application routing import controller monitors the application routing import resources, and modifies the nginx configuration file in real time according to the creation of resources, so as to realize the forwarding of access requests through application routing in the interconnected cluster. And the configuration file is modified in real time according to the resource information, so as to realize the access to the services in the cluster through application routing from outside the cluster. It solves the problem that the native ingress resources in the existing technology cannot realize cross-cluster service access.

[0078] The above is a cross-cluster application routing access method provided by an embodiment of the present application. Based on the same inventive concept, an embodiment of the present application also provides a cross-cluster application routing access system, such as Figure 2 shown. Figure 2 A cross-cluster routing application access system structure diagram provided for the implementation of this application. The system includes:

[0079] The cluster building module 201 is used to build a plurality of clusters; wherein one or more of the plurality of clusters have an application program interface service API Sever that can be accessed in other clusters;

[0080] The delegate cluster setting module 202 is used to set a cluster that the application program interface service API Sever can access in other clusters as a delegate cluster;

[0081] The component deployment module is used to deploy proxy components, application routing import controllers, application routing export controllers, and create application routing export resources;

[0082] A component control module, used to control the application route import controller to listen to the application route import resource;

[0083] The access module 205 is used to access cross-cluster applications based on a preset domain name.

[0084] In the embodiment of the present application, the component deployment module 203 includes:

[0085] The delegate component deployment submodule is used to deploy delegate components;

[0086] A file configuration submodule, used to set a configuration file for the delegate component;

[0087] The monitoring submodule is used to monitor the designated port based on the delegation component and the set configuration file.

[0088] The cross-cluster application routing access system provided by the embodiment of the present application enriches the functions of the container cloud platform by setting up and deploying cluster components, and realizes the automatic discovery of application routing in the interconnected cluster. The application routing import controller monitors the application routing import resources, and modifies the nginx configuration file in real time according to the creation of resources, so as to realize the forwarding of access requests through application routing in the interconnected cluster. And the configuration file is modified in real time according to the resource information, so as to realize the access to the services in the cluster through application routing from outside the cluster. It solves the problem that the native ingress resources in the existing technology cannot realize cross-cluster service access.

[0089] The above is a cross-cluster application routing access method provided by an embodiment of the present application. Based on the same inventive concept, an embodiment of the present application also provides a cross-cluster application routing access device. Figure 3 A schematic diagram of a cross-cluster application routing access device provided in an embodiment of the present application, such as Figure 3 As shown, the device mainly includes: at least one processor 301; and a memory 302 connected to the at least one processor in communication; wherein the memory 302 stores instructions that can be executed by the at least one processor 301, and the instructions are executed by the at least one processor 301, so that the at least one processor 301 can complete: building a plurality of clusters; wherein one or more of the plurality of clusters have an application program interface service API Sever that can be accessed in other clusters;

[0090] Set the cluster that the API Sever can access in other clusters as a delegate cluster;

[0091] Deploy proxy components and application routing import controllers, and create application routing export resources;

[0092] Based on the application route import resource created by the proxy component, control the application route import controller to listen to the application route import resource, and modify the application route import controller;

[0093] Access cross-cluster applications based on preset domain names.

[0094] In addition, the embodiment of the present application further provides a non-volatile computer storage medium for cross-cluster application routing access, storing computer executable instructions, wherein the computer executable instructions are configured to: build a plurality of clusters; wherein one or more of the plurality of clusters have an application program interface service API Sever that can be accessed in other clusters;

[0095] Set the cluster that the API Sever can access in other clusters as a delegate cluster;

[0096] Deploy proxy components and application routing import controllers, and create application routing export resources;

[0097] Based on the application route import resource created by the proxy component, control the application route import controller to listen to the application route import resource, and modify the application route import controller;

[0098] Access cross-cluster applications based on preset domain names.

[0099] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0100] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0101] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0102] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0103] Each embodiment in this application is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0104] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0105] The above is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A cross-cluster application routing access method, characterized in that: The method comprises: Building several clusters; wherein one or more of the several clusters have an application program interface service APIServer that can be accessed by other clusters; Setting a delegate cluster; wherein the application program interface service API Server of the delegate cluster can be accessed through other clusters; deploying a delegate component; setting a configuration file for the delegate component; monitoring a designated port based on the delegate component and the set configuration file; the delegate component respectively establishes connections with multiple interconnected clusters for exchanging metadata between the multiple interconnected clusters; Deploy proxy components, application routing import controllers, application routing export controllers, and create application routing export resources; When the local cluster proxy component detects the creation of an application route export resource, it sends the creation event to the API Server of the delegate cluster. At the same time, the proxy components of other clusters detect the creation of a new application route export resource ingress-export through the API Server of the delegate cluster. At this time, the proxy component creates an application route import resource ingress-import in the local cluster. Control the application route import controller to listen to the application route import resource; Parse the backend service information corresponding to the application routing import resource; based on the parsed backend service information, modify the Nginx configuration file; perform reloading to make the modified Nginx configuration file effective; the modification of the Nginx configuration file based on the parsed backend service information specifically includes: determining whether the application routing import resource has a resource update; wherein the resource update includes: resource creation and resource modification; when the application routing import resource has a resource creation, the domain name specified in the resource is matched with the parsed backend service one by one according to the preset rules and written into the Nginx configuration file; when the application routing import resource has a resource modification, the Nginx configuration file is modified according to the content of the resource modification; Access cross-cluster applications based on preset domain names.

2. A cross-cluster application routing access method according to claim 1, characterized in that: The proxy component, the application routing import controller and the application routing export controller are deployed based on dameonset.

3. A cross-cluster application routing access system, characterized in that: The system comprises: A cluster building module, used to build a number of clusters; wherein one or more of the clusters have an application program interface service API Server that can be accessed in other clusters; The delegate cluster setting module is used to set the cluster that the application program interface service API server can access in other clusters as a delegate cluster; The component deployment module is used to deploy the proxy component, the application routing import controller, the application routing export controller, and create the application routing export resource; the component deployment module includes: a delegate component deployment submodule, used to deploy the delegate component; a file configuration submodule, used to set the configuration file for the delegate component; a monitoring submodule, used to monitor the specified port based on the delegate component and the set configuration file; The component control module is used to control the application routing import controller to listen to the application routing import resources; when the local cluster proxy component listens to the creation of application routing export resources, it will send the creation event to the application interface service APIServer of the delegate cluster. At the same time, the proxy components of other clusters will listen to the creation of new application routing export resources ingress-export resources through the application interface service APIServer of the delegate cluster. At this time, the proxy component will create application routing import resources ingress-import resources in the local cluster; Specifically include: parsing the backend service information corresponding to the application routing import resource; based on the parsed backend service information, modifying the Nginx configuration file; executing reloading to make the modified Nginx configuration file effective; based on the parsed backend service information, modifying the Nginx configuration file specifically includes: determining whether there is a resource update situation of the application routing import resource; wherein the resource update situation includes: resource creation and resource modification; when there is a resource creation of the application routing import resource, the domain name specified in the resource is matched with the parsed backend service one by one according to the preset rules and written into the Nginx configuration file; when there is a resource modification of the application routing import resource, the Nginx configuration file is modified according to the content of the resource modification; The access module is used to access cross-cluster applications based on a preset domain name.

4. A cross-cluster application routing access device, characterized in that: The device comprises: at least one processor; and, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to: Building several clusters; wherein one or more of the clusters have an application program interface service APIServer that can be accessed in other clusters; Setting a cluster that an application program interface service API Server can access in other clusters as a delegate cluster; deploying a delegate component; setting a configuration file for the delegate component; monitoring a designated port based on the delegate component and the set configuration file; the delegate component establishes connections with multiple interconnected clusters respectively, for exchanging metadata between the multiple interconnected clusters; Deploy proxy components and application routing import controllers, and create application routing export resources; When the local cluster proxy component listens to the creation of an application routing export resource, it will send the creation event to the application interface service APIServer of the delegate cluster. At the same time, the proxy components of other clusters will listen to the creation of a new application routing export resource ingress-export resource through the application interface service APIServer of the delegate cluster. At this time, the proxy component will create an application routing import resource ingress-import resource in the local cluster; based on the application routing import resource created by the proxy component, control the application routing import controller to listen to the application routing import resource, and modify the application routing import controller; specifically including: parsing the application routing import resource for According to the backend service information of the application routing import, modify the Nginx configuration file; perform reloading to make the modified Nginx configuration file effective; the modification of the Nginx configuration file based on the backend service information of the application routing import specifically includes: determining whether the application routing import resource has a resource update; wherein the resource update includes: resource creation and resource modification; when the application routing import resource has a resource creation, the domain name specified in the resource is matched with the resolved backend service one by one according to the preset rules and written into the Nginx configuration file; when the application routing import resource has a resource modification, the Nginx configuration file is modified according to the content of the resource modification; Access cross-cluster applications based on preset domain names.

5. A non-volatile computer storage medium for cross-cluster application routing access, storing computer executable instructions, characterized in that: The computer executable instructions are configured to: Building several clusters; wherein one or more of the clusters have an application program interface service APIServer that can be accessed in other clusters; Setting a cluster that the application program interface service API Server can access in other clusters as a delegate cluster; deploying a delegate component; setting a configuration file for the delegate component; monitoring a designated port based on the delegate component and the set configuration file; the delegate component establishes connections with multiple interconnected clusters respectively, for exchanging metadata between the multiple interconnected clusters; Deploy proxy components and application routing import controllers, and create application routing export resources; When the local cluster proxy component listens to the creation of an application routing export resource, it will send the creation event to the application interface service APIServer of the delegate cluster. At the same time, the proxy components of other clusters will listen to the creation of a new application routing export resource ingress-export resource through the application interface service APIServer of the delegate cluster. At this time, the proxy component will create an application routing import resource ingress-import resource in the local cluster; based on the application routing import resource created by the proxy component, control the application routing import controller to listen to the application routing import resource, and modify the application routing import controller; specifically including: parsing the application routing import resource for According to the backend service information of the application routing import, modify the Nginx configuration file; perform reloading to make the modified Nginx configuration file effective; the modification of the Nginx configuration file based on the backend service information of the application routing import specifically includes: determining whether the application routing import resource has a resource update; wherein the resource update includes: resource creation and resource modification; when the application routing import resource has a resource creation, the domain name specified in the resource is matched with the resolved backend service one by one according to the preset rules and written into the Nginx configuration file; when the application routing import resource has a resource modification, the Nginx configuration file is modified according to the content of the resource modification; Access cross-cluster applications based on preset domain names.