WO2021249268A1

WO2021249268A1 - Method for creating service mesh instance, service mesh system, and multi-cluster system

Info

Publication number: WO2021249268A1
Application number: PCT/CN2021/098052
Authority: WO
Inventors: 王夕宁
Original assignee: 阿里巴巴集团控股有限公司
Priority date: 2020-06-09
Filing date: 2021-06-03
Publication date: 2021-12-16
Also published as: CN113296927A

Abstract

Disclosed are a method for creating a service mesh instance, a service mesh system, and a multi-cluster system. The method comprises: creating a service mesh instance in a first runtime environment; registering multiple service instances in a second runtime environment to the service mesh instance; and deploying a data plane component of the service mesh instance into the second runtime environment, deploying a control plane component, used for providing a strategy and/or a configuration for the data plane component, of the service mesh instance into the first runtime environment, and issuing parameters of the control plane component into the second runtime environment, so that the data plane component can implement invocation among different service instances by following the strategy and/or the configuration provided by the control plane component. Therefore, a service mesh instance and life cycle management of service runtime environments can be decoupled, thereby providing support for the implementation of hosting of the service mesh instance.

Description

Construction method of service grid instance, service grid system and multi-cluster system

This application claims the priority of the Chinese patent application with the application number 202010516849.X and the invention title of "Service Grid Instance Construction Method, Service Grid System and Multi-cluster System" filed on June 9, 2020, and its entire contents Incorporated in this application by reference.

Technical field

The present disclosure relates to the field of computer technology, and in particular to a method for constructing a service grid instance, a service grid system, and a multi-cluster system.

Background technique

Microservices refers to exposing data and functions as a set of loosely coupled API services, and then combining these API services to solve application requirements. With the help of microservices, organizations can quickly adapt to changing customer needs and provide combined services that can create a competitive advantage.

As the complexity of application functions increases and there are more and more microservices, these loosely coupled services need to understand the dependencies between services to minimize the trouble of making changes in the future.

The service grid is a key part of the microservice infrastructure, which can implement calls between services and improve the flexibility and security of applications. Existing service grid construction solutions usually build service grid instances in a microservice architecture to provide governance and traffic management capabilities for multiple services in the microservice architecture. However, this approach has certain drawbacks, including: the control plane is A single point of failure and a single configuration error may cause the entire control and data plane to fail; the complexity of the control plane configuration requires user maintenance and management, which cannot be managed; the service grid instance is tightly coupled with the lifecycle management of the service runtime environment.

Therefore, there is a need for a service grid construction solution that can solve at least one of the above-mentioned drawbacks.

Summary of the invention

A technical problem to be solved by the present disclosure is to provide a service grid construction solution that can solve at least one of the above-mentioned drawbacks.

According to a first aspect of the present disclosure, a method for constructing a service grid instance is provided, which includes: creating a service grid instance in a first operating environment; and registering multiple service instances in a second operating environment to the service Grid instance; deploy the data plane components of the service grid instance to the second operating environment, and deploy the control plane components of the service grid instance that are used to provide strategies and/or configurations for the data plane components to the first operating environment , And deliver the parameters of the control plane component to the second operating environment, so that the data plane component can follow the provision strategy and/or configuration provided by the control plane component to implement calls between different service instances.

According to a second aspect of the present disclosure, there is also provided an application running method. The application includes multiple service instances located in a second running environment. The method includes: using data plane components deployed in the second running environment to implement different Calls between service instances, where the control plane components used to provide strategies and/or configurations for the data plane components are deployed in a first operating environment that is different from the second operating environment, and the data plane components and the control plane components constitute multiple A service grid instance of a service instance.

According to the third aspect of the present disclosure, a service grid system is also provided, including: one or more service grid instances, the service grid instances are used to implement calls between different service instances on multiple clusters, and the service grid The data plane components of the grid instance are deployed on multiple clusters, and the control plane components of the service grid instance are deployed in the service grid system. The control plane components are used to provide strategies and/or configurations for the data plane components, and the service grid system Distribute the parameters of the control plane component to multiple clusters, so that the data plane component can follow the provision strategy and/or configuration provided by the control plane component to implement calls between different service instances.

According to the fourth aspect of the present disclosure, a multi-cluster system is also provided, including: multiple clusters, each of which is deployed with one or more service instances; a cluster access controller, used to connect multiple clusters A service grid instance deployed in a service grid system; multiple agent containers, each agent container corresponds to a service instance, the service instance calls the corresponding agent container to communicate with the agent containers corresponding to other service instances; the agent container passes The access portal provided by the portal gateway component deployed in the service grid system obtains the parameters of the control plane component of the service instance.

According to a fifth aspect of the present disclosure, there is provided a computing device, including: a processor; and a memory on which executable code is stored. When the executable code is executed by the processor, the processor is caused to execute the first The method described in the aspect.

According to a sixth aspect of the present disclosure, there is provided a non-transitory machine-readable storage medium having executable code stored thereon, and when the executable code is executed by a processor of an electronic device, the processor executes the above-mentioned The method described in one aspect.

Therefore, by deploying the control plane components and the data plane components in different operating environments, the life cycle management of the service grid instance and the service runtime environment can be decoupled, which provides support for realizing the hosting of the service grid instance.

Description of the drawings

Through a more detailed description of the exemplary embodiments of the present disclosure in conjunction with the accompanying drawings, the above and other objectives, features, and advantages of the present disclosure will become more apparent. Among them, in the exemplary embodiments of the present disclosure, the same reference numerals generally represent The same parts.

Fig. 1 shows a schematic principle diagram of a method for constructing a service grid instance according to an embodiment of the present disclosure;

Figure 2 shows a schematic diagram of the structure of a service grid system and related components deployed in a multi-cluster environment according to an embodiment of the present disclosure;

FIG. 3 shows a schematic diagram of deploying a proxy container and a process of a non-containerized application together according to an embodiment of the present disclosure;

Fig. 4 shows a schematic structural diagram of a computing device according to an embodiment of the present disclosure.

detailed description

Hereinafter, preferred embodiments of the present disclosure will be described in more detail with reference to the accompanying drawings. Although the preferred embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure can be implemented in various forms and should not be limited by the embodiments set forth herein. On the contrary, these embodiments are provided to make the present disclosure more thorough and complete, and to fully convey the scope of the present disclosure to those skilled in the art.

The service grid is mainly composed of two key components: the data plane and the control plane.

In the data plane, the application service deployment is modified to include a dedicated agent component (corresponding to the agent container mentioned below, such as the Sidecar agent). The data plane makes each service not directly call the service through the network, but call its local proxy component to communicate with proxy components in other services. The proxy component encapsulates the complex logic of service-to-service exchange. A group of interconnected proxy components in the service grid constitute the entire data plane.

The control plane is used to provide policies and/or configurations for the data plane. In other words, the control plane is used to control the agent behavior on the entire service grid. It is possible to specify service routing rules and authentication strategies on the control plane as a whole, or to collect indicators and configure data plane parameters. Generally speaking, the communication between the data plane and the control plane is regulated through API definitions.

This disclosure proposes a managed service grid construction solution. By deploying the control plane components and data plane components of the service grid in different operating environments, the life cycle of the service grid instance and the service runtime environment can be decoupled Management to realize the hosting of control plane components.

Fig. 1 shows a schematic principle diagram of a method for constructing a service grid instance according to an embodiment of the present disclosure. Referring to Figure 1, the second operating environment refers to the operating environment in which the service instance is located, and multiple service instances can be deployed in the second operating environment. The first operating environment is different from the second operating environment. The first operating environment refers to the hosting environment of the service grid, that is, the environment used to create the service grid instance.

A service grid instance can be created in the first operating environment, and multiple service instances located in the second operating environment can be registered with the service grid instance.

The service grid instance mainly includes data plane components and control plane components. In the present disclosure, the data plane component can be separated from the service grid instance, and the data plane component can be deployed in the second operating environment. The control plane components used to provide policies and/or configurations for the data plane components are retained in the service grid instance, that is, the control plane components are deployed in the first operating environment. The parameters of the control plane component are delivered to the second operating environment in a predetermined manner, so that the data plane component can follow the provision strategy and/or configuration provided by the control plane component to implement calls between different service instances.

In response to the update of the control plane component in the first operating environment, the parameters of the updated control plane component can be issued to the second operating environment, so that the data plane component can follow the provision strategy and provision provided by the updated control plane component. / Or configuration to implement calls between different service instances. Among them, the operation of updating the control plane components can be performed by the user, or can be performed by the system that provides the service grid hosting service (the hosting service grid system described below).

As an example, the first operating environment may refer to a managed service grid system based on a public cloud, a private cloud, or a hybrid cloud, that is, the managed service grid system may be deployed on a public cloud, a private cloud, or a hybrid cloud. The second operating environment may be a multi-cluster environment. A cluster refers to a collection of logically grouped computer resources running as a unit, which can be an independent physical cluster or a logical cluster group containing multiple physical clusters, such as a Kubernetes cluster. One or more service instances can be deployed in each cluster. All service instances deployed in a multi-cluster environment can form a complete application architecture (such as a microservice architecture).

The hosting service grid system provides external hosting services for service grid instances. The method for constructing a service grid instance of the present disclosure can be executed by a managed service grid system, and a service grid instance can be created for service instances deployed on multiple clusters, so as to implement calls between different service instances.

By deploying control plane components and data plane components in different operating environments, the life cycle management of service grid instances and service runtime environments can be decoupled to a certain extent. Taking the second operating environment as a hosted service grid system as an example, the configuration parameters of the control plane components can be set and updated by hosting, that is, the hosted service grid system can maintain the configuration of the control plane components without the need for users Maintain the configuration complexity of the control plane.

And because the control plane components and data plane components are deployed in different operating environments, even if parameter configuration errors occur during the update of the control plane components, the data plane components can follow the strategy and/or configuration provided by the original control plane components without causing The entire data plane fails.

Taking the first operating environment as a hosted service grid system and the second operating environment as a multi-cluster environment as an example, the service grid instance may also include a service registration controller and a service registration library. Among them, the service registration controller and the service registration library are deployed in a managed service grid system, and a cluster access controller is also provided in a multi-cluster environment. Multiple clusters can be connected to the service grid instance by the cluster access controller; different service instances on multiple clusters can be registered to the service grid instance by the service registration controller; different service instances on multiple clusters can be registered by the service registry The service registration information of the service instance is managed in a unified manner.

The present disclosure can also deploy the ingress gateway component in the service grid instance to the first operating environment, and the ingress gateway component is used to provide an access portal for the data plane component. For example, the entry gateway component can be an access entry that provides control plane parameters to the data plane, and can be implemented by a load balancer in an intranet or a private network.

The data plane component may include multiple proxy containers, and each proxy container corresponds to a service instance. The service instance can call the corresponding proxy container to communicate with the proxy container corresponding to other service instances, so as to implement calls between different service instances.

The proxy container can be deployed as an out-of-process Sidecar with application instances and is responsible for performing network-level operations and observing all inbound and outbound traffic. Service instances can be divided into containerized applications and non-containerized application processes. For service instances belonging to containerized applications, the proxy container can be deployed together with the container where the application of the service instance is located; for service instances belonging to the process of non-containerized applications, the node where the process is located can be registered as the working node of the second operating environment , Through the container runtime management environment in the second runtime environment to coordinate the interaction between the process and the agent container corresponding to the process.

The present disclosure can also deliver remote service grid metadata related to the configuration parameters of the service instance to the second operating environment, so that the components related to the service grid instance deployed in the second operating environment can be based on the remote service network Grid metadata is synchronized.

As described above, the method for constructing a service grid instance of the present disclosure can be executed by a service grid system for providing service grid hosting services. The details involved in the present disclosure will be further described below in conjunction with the service grid system.

Fig. 2 shows a schematic diagram of the structure of a service grid system and related components deployed in a multi-cluster environment according to an embodiment of the present disclosure.

As shown in FIG. 2, the service grid system 101 provides a capability for externally exposing the control plane of the service grid in a hosted manner. A hosted service grid system 101 can construct multiple different service grid instances 102.

The service grid instance 102 is used to implement calls between different service instances on multiple clusters. Each service grid instance 102 provides a complete service grid control plane 104 (corresponding to the control plane components mentioned above), and the data plane components of the service grid instance 102 are deployed on multiple clusters. The service grid control plane 104 is used to provide policies and/or configurations for data plane components. The service grid system 101 can deliver the parameters of the service grid control plane 104 to multiple clusters so that the data plane components can follow the control plane The provision strategy and/or configuration provided by the component to implement calls between different service instances.

The components related to the service grid instance 102 deployed on multiple clusters constitute a multi-cluster data plane. The multi-cluster data plane includes a cluster access controller 108, and the cluster access controller 108 can connect multiple clusters to the service grid instance 101. The service grid instance 102 can include a service registration controller 109 and a service registration library 110. In response to the cluster access controller 108 connecting multiple clusters to the service grid instance 101, the service registration controller 109 can connect multiple clusters to the service grid instance 101. The different service instances of are registered to the service grid instance 101. The service registration controller 109 can simultaneously support unified discovery and registration of services across multiple clusters; each service in the cluster does not depend on other settings and supports any type of exposure mode. As an example, the service grid instance 102 can manage routing rule definitions with a declarative API, thereby exposing service endpoints to the service registry in a declarative method. Among them, service discovery refers to the process of locating service endpoints from the cluster according to the service name.

The service registry 110 can uniformly manage the service registration information of different service instances on multiple clusters. For example, the service registry 110 uniformly manages the registration service information processed by the service registration controller 109, and uniformly stores all the registration service information in a standardized manner.

The service grid instance 102 also includes a service grid controller 103 and a service grid entry gateway 105 (corresponding to the entry gateway component mentioned above). The service grid controller 103 is used to set up a service grid control plane 104 and a service grid entry gateway 105, and the service grid entry gateway 105 is used to provide access to the service grid control plane 104 for multiple clusters.

Specifically, the service grid controller 103 provides the ability to decouple the lifecycle management of the service grid instance and the service runtime environment; supports the dynamic creation of the service grid control plane 104 and the service grid entry gateway 105, and supports The configuration parameters of the service grid are dynamically synchronized to update the hosted service grid control plane 104 and the service grid entry gateway 105.

The service grid control plane 104 runs in the service grid system 101, provides traffic configuration and control options for agents in the service grid data plane, and can provide flexibility, load balancing, and traffic control functions. The service grid entry gateway 105 is an access entry that provides the managed service grid control plane 104 to multiple clusters of the data plane, and is often implemented by a load balancer of an intranet or a private network.

The service grid instance 102 also includes a remote service grid controller 106, which is used to deliver remote service grid metadata 107 related to the configuration parameters of the service instance to multiple clusters, so as to be deployed on multiple clusters and services. Components related to the grid instance can be synchronized with the service grid instance 101 based on the remote service grid metadata 107.

In other words, the remote service grid controller 106 provides the ability to remotely distribute the remote service grid metadata 107 to the cluster in the service grid, and supports the dynamic synchronization update based on the configuration parameters of the service grid to be sent to the data plane. Remote service grid metadata 107 on the cluster. The remote service grid metadata 107 is used to dynamically synchronize the service grid related components and configuration parameters on the data plane multi-cluster to support the proxy container 111 to dynamically adjust with the change of the control plane parameters to ensure that the service grid entry gateway 105 connection capabilities.

Service instances deployed on multiple clusters can be divided into containerized application and non-containerized application processes. For service instances belonging to containerized applications, the proxy container 111 can be deployed as an out-of-process Sidecar together with the application container 112 of the service instance, and is responsible for performing network-level operations and observing all inbound and outbound traffic. The application container 112 refers to the container where the application of the service instance is located, and calls between applications are controlled by the proxy container 111 to intercept flow.

The process of non-containerized applications cannot be processed through containerization, and usually needs to share a host network with the proxy container 111. For service instances of processes of non-containerized applications, the application process injector 113 deployed in a multi-cluster environment can register the node where the process is located as a worker node of the cluster, and coordinate the process and the process through the container runtime management environment in the cluster. The interaction between the agent containers 111 corresponding to the process. As shown in Figure 3, the agent container and application process can be deployed in a pod. After the node where the process is located is registered as a working node of the cluster, the Pod can use the network space and network resources of the node through the Host network.

In summary, through the service grid controller 103 and the remote service grid controller 106, a method and system for hosting service grids supporting multi-cluster management are proposed, and a highly available way to achieve cross-cluster service registration is provided. , Service discovery and traffic routing management; the service grid controller 103 provides the ability to decouple the life cycle management of the service grid instance and the service runtime environment; supports the dynamic creation of the managed service grid control plane 104 and service grid entry The gateway 105 supports the dynamic and synchronous update of the managed service grid control plane 104 and the service grid entry gateway 105 based on the configuration parameters of the service grid; the service registration controller 109 supports the registration of different service instances on multiple clusters to one service network Lattice instances can support unified discovery and registration of services across multiple clusters; each service in the cluster does not depend on other settings and supports any type of exposure method; supports containerized applications and non-containerized applications through the application process injector 113 Unified management.

The present disclosure also proposes an application running method. The application mentioned in this embodiment may refer to an application including multiple service instances, that is, an application based on a microservice architecture. The operating environment where the multiple service instances are located is the second operating environment mentioned above. The service grid construction scheme mentioned above can be used to construct corresponding service grid instances for these multiple service instances. For the construction process of the service grid instances, please refer to the relevant description above, which will not be repeated here.

In the application running process, when calls between service instances are required, the data plane components deployed in the second operating environment can be used to implement calls between different service instances. Wherein, as described in the construction scheme of the service grid instance above, the control plane component used to provide strategy and/or configuration for the data plane component is deployed in a first operating environment different from the second operating environment, and the data plane component and control The plane component constitutes a service grid instance for these multiple service instances.

As an example, the data plane component may include multiple proxy containers, and each proxy container corresponds to a service instance. When a certain service instance of the multiple service instances needs to call another service instance, the service instance belonging to the caller can call the corresponding proxy container to communicate with the proxy container corresponding to the other service instances belonging to the callee. For the proxy container and service instance, please refer to the relevant description above, which will not be repeated here.

The present disclosure also provides a multi-cluster system, including: multiple clusters, one or more service instances are deployed on each cluster, multiple clusters may refer to a cluster combination composed of more than one cluster, for example, it may refer to Cluster federation formed by multiple Kubernetes clusters; cluster access controller, used to connect multiple clusters to service grid instances deployed in the service grid system; multiple agent containers, each agent container corresponding to a service instance , The service instance calls the corresponding proxy container to communicate with the proxy container corresponding to other service instances; the proxy container obtains the parameters of the control plane component of the service instance through the access portal provided by the entry gateway component deployed in the service grid system.

Application instances are divided into containerized application and non-containerized application processes. The multi-cluster system also includes: application process injector, which is used to register the node where the process of non-containerized application is located as the working node of the cluster, and run through the container of the cluster The time management environment coordinates the interaction between the process and the agent container corresponding to the process.

The multi-cluster system can also receive remote service grid metadata related to the configuration parameters of the service instance sent by the service grid system, and the components related to the service instance deployed in the multi-cluster system (such as cluster access controller, agent container) ) Synchronization can be based on remote service grid metadata. For the details involved in the multi-cluster system, please refer to the relevant description above, which will not be repeated here.

Fig. 4 shows a schematic structural diagram of a computing device that can be used to implement the above-mentioned method for constructing a service grid instance according to an embodiment of the present invention.

Referring to FIG. 4, the computing device 400 includes a memory 410 and a processor 420.

The processor 420 may be a multi-core processor, or may include multiple processors. In some embodiments, the processor 420 may include a general-purpose main processor and one or more special co-processors, such as a graphics processing unit (GPU), a digital signal processor (DSP), and so on. In some embodiments, the processor 420 may be implemented using a customized circuit, such as an Application Specific Integrated Circuit (ASIC) or a Field Programmable Gate Array (FPGA, Field Programmable Gate Arrays).

The memory 410 may include various types of storage units, such as a system memory, a read only memory (ROM), and a permanent storage device. Among them, the ROM may store static data or instructions required by the processor 420 or other modules of the computer. The permanent storage device may be a readable and writable storage device. The permanent storage device may be a non-volatile storage device that does not lose stored instructions and data even after the computer is powered off. In some embodiments, the permanent storage device adopts a large-capacity storage device (such as a magnetic or optical disk, flash memory) as the permanent storage device. In other embodiments, the permanent storage device may be a removable storage device (for example, a floppy disk, an optical drive). The system memory can be a readable and writable storage device or a volatile readable and writable storage device, such as dynamic random access memory. The system memory can store some or all of the instructions and data needed by the processor at runtime. In addition, the memory 410 may include any combination of computer-readable storage media, including various types of semiconductor memory chips (DRAM, SRAM, SDRAM, flash memory, programmable read-only memory), and magnetic disks and/or optical disks may also be used. In some embodiments, the memory 410 may include a removable storage device that can be read and/or written, such as a compact disc (CD), a read-only digital versatile disc (for example, DVD-ROM, dual-layer DVD-ROM), Read-only Blu-ray discs, ultra-density discs, flash memory cards (such as SD cards, min SD cards, Micro-SD cards, etc.), magnetic floppy disks, etc. The computer-readable storage medium does not contain carrier waves and instantaneous electronic signals that are transmitted wirelessly or wiredly.

The memory 410 stores executable codes. When the executable codes are processed by the processor 420, the processor 420 can be made to execute the method for constructing the service grid instance mentioned above.

The construction method of the service grid instance, the service grid system, the application operation method and the multi-cluster system according to the present invention have been described in detail above with reference to the accompanying drawings.

In addition, the method according to the present invention can also be implemented as a computer program or computer program product. The computer program or computer program product includes computer program code instructions for executing the above-mentioned steps defined in the above-mentioned method of the present invention.

Alternatively, the present invention can also be implemented as a non-transitory machine-readable storage medium (or computer-readable storage medium, or machine-readable storage medium) on which executable code (or computer program, or computer instruction code) is stored ), when the executable code (or computer program, or computer instruction code) is executed by the processor of the electronic device (or computing device, server, etc.), the processor is caused to execute each step of the above method according to the present invention .

Those skilled in the art will also understand that the various exemplary logic blocks, modules, circuits, and algorithm steps described in conjunction with the disclosure herein can be implemented as electronic hardware, computer software, or a combination of both.

The flowcharts and block diagrams in the accompanying drawings show the possible implementation architecture, functions, and operations of the system and method according to multiple embodiments of the present invention. In this regard, each block in the flowchart or block diagram may represent a module, program segment, or part of the code, and the module, program segment, or part of the code contains one or more modules for realizing the specified logical function. Executable instructions. It should also be noted that, in some alternative implementations, the functions marked in the blocks may also occur in a different order than marked in the drawings. For example, two consecutive blocks can actually be executed substantially in parallel, or they can sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block in the block diagram and/or flowchart, and the combination of the blocks in the block diagram and/or flowchart, can be implemented by a dedicated hardware-based system that performs the specified functions or operations Or it can be realized by a combination of dedicated hardware and computer instructions.

The embodiments of the present invention have been described above, and the above description is exemplary, not exhaustive, and is not limited to the disclosed embodiments. Without departing from the scope and spirit of the described embodiments, many modifications and changes are obvious to those of ordinary skill in the art. The choice of terms used herein is intended to best explain the principles, practical applications, or improvements to the technology in the market for each embodiment, or to enable those of ordinary skill in the art to understand the various embodiments disclosed herein.

Claims

A method for constructing a service grid instance includes:

Create a service grid instance in the first operating environment;

Register multiple service instances located in the second operating environment with the service grid instance;

The data plane component of the service grid instance is deployed to the second operating environment, and the control plane component of the service grid instance used to provide policies and/or configurations for the data plane component is deployed to all In the first operating environment, and sending the parameters of the control plane component to the second operating environment, so that the data plane component can follow the provision strategy and/or configuration provided by the control plane component , To implement calls between different service instances.
The method according to claim 1, further comprising:

The ingress gateway component in the service grid instance is deployed in the first operating environment, and the ingress gateway component is used to provide an access portal for the data plane component.
The method of claim 1, wherein:

The data plane component includes a plurality of proxy containers, each of the proxy containers corresponds to a service instance, and the service instance calls the corresponding proxy container to communicate with the proxy containers corresponding to other service instances.
The method according to claim 3, further comprising:

For service instances belonging to containerized applications, deploy the proxy container and the container where the application of the service instance is located together; and/or

For a service instance belonging to a process of a non-containerized application, the node where the process is located is registered as a working node of the second operating environment, and the process is coordinated with and with the container runtime management environment in the second operating environment. The interaction between the agent containers corresponding to the process.
The method of claim 1, wherein:

The first operating environment is a service grid system based on public cloud, private cloud or hybrid cloud, and the second operating environment is a multi-cluster environment.
The method according to claim 5, wherein the service grid instance further includes a service registration controller and a service registration library, and a cluster access controller is also provided in the multi-cluster environment, and the service grid instance is located in the second operation The steps of registering multiple service instances in the environment to the service grid instance include:

Connecting multiple clusters to the service grid instance by the cluster access controller;

Registering different service instances on the multiple clusters with the service grid instance by the service registration controller;

The service registration library performs unified management of service registration information of different service instances on the multiple clusters.
The method according to claim 1, further comprising:

Distribute the remote service grid metadata related to the configuration parameters of the service instance to the second operating environment, so that the components related to the service grid instance deployed in the second operating environment can Synchronize based on the remote service grid metadata.
An application operating method, the application including multiple service instances located in a second operating environment, the method including:

The data plane components deployed in the second operating environment are used to implement calls between different service instances, wherein the control plane components used to provide policies and/or configurations for the data plane components are deployed to be different from the first In the first operating environment of the second operating environment, the data plane component and the control plane component constitute a service grid instance for the multiple service instances.
The method according to claim 8, wherein:

The data plane component includes a plurality of proxy containers, each of the proxy containers corresponds to a service instance, and the service instance calls the corresponding proxy container to communicate with the proxy containers corresponding to other service instances.
A service grid system includes: one or more service grid instances,

The service grid instance is used to implement calls between different service instances on multiple clusters,

The data plane component of the service grid instance is deployed on the multiple clusters, the control plane component of the service grid instance is deployed in the service grid system, and the control plane component is used to provide the data Plane components provide strategy and/or configuration,

The service grid system issues the parameters of the control plane component to the multiple clusters, so that the data plane component can follow the provision strategy and/or configuration provided by the control plane component to achieve different Calls between service instances.
The service grid system according to claim 10, wherein:

The service grid instance further includes a service grid controller and an ingress gateway component, the service grid controller is used to set the control plane component and the ingress gateway component, and the ingress gateway component is used to provide services for the multiple A cluster provides access to the control plane components.
The service grid system according to claim 10, wherein:

The service grid instance further includes a remote service grid controller, configured to deliver remote service grid metadata related to the configuration parameters of the service instance to the multiple clusters so as to be deployed in the multiple clusters. The components on the cluster related to the service grid instance can be synchronized with the service grid instance based on the remote service grid metadata.
The service grid system according to claim 10, wherein:

The service grid instance also includes a service registration controller and a service registration library,

In response to the cluster access controller deployed on the multiple clusters accessing the multiple clusters to the service grid instance, the service registration controller registers different service instances on the multiple clusters with For the service grid instance, the service registry database performs unified management of service registration information of different service instances on the multiple clusters.
A multi-cluster system, including:

Multiple clusters, one or more service instances are deployed on each of the clusters;

A cluster access controller, configured to connect the multiple clusters to a service grid instance deployed in a service grid system;

A plurality of agent containers, each of the agent containers corresponds to a service instance, and the service instance calls the corresponding agent container to communicate with the agent containers corresponding to other service instances;

The proxy container obtains the parameters of the control plane component of the service instance through the access portal provided by the portal gateway component deployed in the service grid system.
The multi-cluster system according to claim 14, wherein the application instances are divided into the process of containerized applications and non-containerized applications, and the multi-cluster system further comprises:

The application process injector is used to register the node where the process of the non-containerized application is located as the working node of the cluster, and coordinate the interaction between the process and the agent container corresponding to the process through the container runtime management environment of the cluster.
The multi-cluster system according to claim 14, wherein:

The multi-cluster system also receives remote service grid metadata related to the configuration parameters of the service instance sent by the service grid system, and the components related to the service instance deployed in the multi-cluster system are based on The remote service grid metadata is synchronized.
A computing device including:

Processor; and

The memory has executable code stored thereon, and when the executable code is executed by the processor, the processor is caused to execute the method according to any one of claims 1 to 9.
A non-transitory machine-readable storage medium with executable code stored thereon. When the executable code is executed by a processor of an electronic device, the processor is caused to execute any one of claims 1 to 9 The method described.