WO2024193085A1 - Gateway service request processing method and device, and cloud native gateway system management method and device - Google Patents

Abstract

The present disclosure provides a gateway service processing method and device, and a cloud native gateway system management method and device, capable of being applied to the technical fields of networks and cloud native. The gateway service request processing method comprises: in response to receiving a gateway service request to be processed, according to a preset mapping relationship and gateway service configuration information to be processed in said gateway service request, determining target gateway cluster information corresponding to a target gateway cluster, target gateway information corresponding to a target gateway, and target service information corresponding to a target service; according to the target gateway cluster information, the target gateway information, and the target service information, determining the operating state of at least one container group corresponding to the target service; according to the operating state of the at least one container group corresponding to the target service, determining a target container group among the at least one container group; and sending said gateway service request to the target container group, such that the target container group processes said gateway service request.

Description

Processing of gateway service requests, management method and device of cloud native gateway system

This application claims priority to Chinese Patent Application No. 202310288631.7 filed on March 22, 2023, the contents of which are incorporated herein by reference.

Technical Field

The present disclosure relates to the fields of network technology and cloud native technology, and more specifically, to a method for processing a service request, a method and device for managing a cloud native gateway system, an electronic device, a computer-readable storage medium, and a computer program product.

Background Art

API (Application Programming Interface) gateway can refer to a unified entry point on the system boundary for external access to internal interface services. Kubernetes can include a collection of API resources based on different gateway definitions.

For example, the Ingress API resource collection based on the Ingress gateway definition and the Gateway API resource collection based on the Gateway gateway definition.

In the process of implementing the concept of the present disclosure, the inventors found that there are at least the following problems in the related technology: it is impossible to ensure high availability of resources and services in Kubernetes.

Summary of the invention

In view of this, the present disclosure provides a method for processing a service request, a method and device for managing a cloud native gateway system, an electronic device, a computer-readable storage medium, and a computer program product.

According to one aspect of the present disclosure, a method for processing a gateway service request is provided, comprising:

In response to receiving the pending gateway service request, determining the target gateway cluster information corresponding to the target gateway cluster, the target gateway information corresponding to the target gateway, and the target gateway information corresponding to the target gateway according to the preset mapping relationship and the pending gateway service configuration information in the pending gateway service request. Target service information corresponding to the target service;

Determine the operating status of at least one container group corresponding to the target service according to the target gateway cluster information, the target gateway information and the target service information;

Determining a target container group from the at least one container group corresponding to the target service according to the respective running states of the at least one container group; and

The to-be-processed gateway service request is sent to the target container group, so that the target container group processes the to-be-processed gateway service request.

According to an embodiment of the present disclosure, in response to receiving a pending gateway service request, determining the target gateway cluster information corresponding to the target gateway cluster, the target gateway information corresponding to the target gateway, and the target service information corresponding to the target service according to the preset mapping relationship and the pending gateway service configuration information in the pending gateway service request includes:

Determine the target virtual Internet Protocol address information according to the gateway service configuration information to be processed;

Determine the target gateway cluster information corresponding to the target gateway cluster according to the first preset mapping relationship and the target virtual Internet Protocol address information;

According to the target gateway cluster information, determine the gateway address information corresponding to the target gateway and the service port information corresponding to the target service;

Determine the target gateway information according to the second preset mapping relationship and the gateway address information; and

The target service information is determined according to the third preset mapping relationship and the service port information.

According to an embodiment of the present disclosure, the target gateway cluster includes at least one gateway, each of the at least one gateway corresponds to at least one service, each of the at least one gateway corresponds to gateway address information, and each of the at least one service corresponds to service port information.

According to an embodiment of the present disclosure, the determining of the gateway address information corresponding to the target gateway and the service port information corresponding to the target service according to the target gateway cluster information includes:

According to the above target gateway cluster information, determine the network segment range of the above target gateway cluster

For each of the at least one gateway, determine the gateway address information corresponding to the gateway according to the network segment range of the target gateway cluster; and

For each of the at least one service corresponding to the gateway, the service port information of the service corresponding to the gateway is determined according to the gateway address information corresponding to the gateway.

According to an embodiment of the present disclosure, in response to receiving the service request to be processed, determining the target virtual Internet Protocol address information according to the gateway service configuration information to be processed includes:

In response to receiving the above-mentioned pending gateway service request, parsing the above-mentioned pending gateway service configuration information to obtain domain name information corresponding to the above-mentioned pending gateway service request; and

According to the above domain name information, the above target virtual network address information is determined.

According to an embodiment of the present disclosure, the first preset mapping relationship includes at least one second key-value relationship, the second key-value relationship includes second key information and second value information, and the at least one second key-value relationship is constructed in the following manner:

For each second key-value relationship in the at least one second key-value relationship, in response to receiving a gateway creation instruction, obtaining a gateway identifier, gateway configuration information, and a gateway cluster identifier;

According to the gateway cluster identifier, determine the virtual network address information corresponding to the gateway cluster identifier;

Determine the gateway address information corresponding to the gateway identifier according to the target routing protocol and the virtual network address information;

Determine the virtual gateway address information as the second key information;

Determine the gateway configuration information as the second value information; and

The second key-value relationship is constructed according to the second key information and the second value information.

According to an embodiment of the present disclosure, when the target routing protocol is a border gateway protocol, determining the gateway address information corresponding to the gateway identifier according to the target routing protocol and the virtual network address information includes:

According to the virtual Internet Protocol address information, configuring a first resource pool, wherein the first resource pool includes at least one first candidate address information;

According to the first resource pool, determining target address information from the at least one first candidate address information; and

According to the border gateway protocol, the target address information is published via any two front-end proxies so as to determine the target address information as the gateway address information.

According to an embodiment of the present disclosure, when the target routing protocol is an equal-cost multi-path routing protocol, determining the gateway address information corresponding to the gateway identifier according to the target routing protocol and the virtual network address information includes:

According to the virtual Internet Protocol address information, configuring a second resource pool, wherein the second resource pool includes at least one second candidate address information;

According to the second resource pool, determining target address information in the at least one second candidate address information;

According to the equal-cost multi-path routing protocol, configure equal-cost routing information corresponding to the target address information; and

The above-mentioned equivalent routing information is determined as the above-mentioned gateway address information.

According to an embodiment of the present disclosure, the second preset mapping relationship includes at least one third key-value relationship, the third key-value relationship includes third key information and third value information, and the at least one third key-value relationship is constructed in the following manner:

For each third key-value relationship of the at least one third key-value relationship, in response to receiving a service creation instruction, obtaining a service identifier, service configuration information, and a gateway identifier;

According to the above gateway identifier, determine the gateway address information corresponding to the above gateway identifier;

Determine the service port information corresponding to the service identifier according to the gateway address information;

Determine the service port information as the third key information;

Determine the service configuration information as the third value information; and

The third key-value relationship is constructed according to the third key information and the third value information.

According to an embodiment of the present disclosure, the target service information includes container group address information corresponding to each of the at least one container group.

According to an embodiment of the present disclosure, the at least one corresponding to the target service is determined based on the target gateway cluster information, the target gateway information and the target service information. The running status of each container group includes:

For each container group address information in at least one container group address information, establishing a detection network connection with the container group according to the container group address information;

In the case where a heartbeat detection packet sent by the container group is received within a predetermined period of time, determining that the operation state of the container group is a normal operation state; and

When no heartbeat detection packet sent by the container group is received within the predetermined period, it is determined that the operation state of the container group is in an abnormal operation state.

According to an embodiment of the present disclosure, the step of determining a target container group in the at least one container group corresponding to the target service according to the respective running states of the at least one container group includes:

In response to the running state of the container group being a normal running state, the container group is determined as the target container group.

According to an embodiment of the present disclosure, sending the to-be-processed gateway service request to the target container group includes:

Determine the target container group address information corresponding to the target container group;

According to the target container group address information, establish an actual network connection with the target container group; and

Based on the actual network connection, the to-be-processed service request is sent to the target container group.

According to another aspect of the present disclosure, a method for managing a cloud native gateway system is provided, including:

Using the gateway service request processing method, processing the target gateway service request to obtain a processing result, wherein the target gateway service request includes target gateway service configuration information, and the target gateway service configuration information is associated with the cloud native gateway system; and

Based on the above processing results, the above cloud native gateway system is managed.

According to another aspect of the present disclosure, a gateway service request processing device is provided, including:

The first determining module is configured to, in response to receiving a pending gateway service request, determine, according to a preset mapping relationship and the pending gateway service configuration information in the pending gateway service request, Determine the target gateway cluster information corresponding to the target gateway cluster, the target gateway information corresponding to the target gateway, and the target service information corresponding to the target service;

A second determination module is used to determine the respective running status of at least one container group corresponding to the target service according to the target gateway cluster information, the target gateway information and the target service information;

A third determining module, configured to determine a target container group from the at least one container group corresponding to the target service according to the respective running states of the at least one container group.

The sending module is used to send the to-be-processed gateway service request to the target container group, so that the target container group processes the to-be-processed gateway service request.

According to another aspect of the present disclosure, a management device for a cloud native gateway system is provided, including:

a processing module, configured to process a target gateway service request using a processing device for a gateway service request to obtain a processing result, wherein the target gateway service request includes target gateway service configuration information, and the target gateway service configuration information is associated with a cloud native gateway system; and

The management module is used to manage the cloud native gateway system according to the processing results.

According to another aspect of the present disclosure, there is provided an electronic device, including:

one or more processors;

a memory for storing one or more instructions,

When the one or more instructions are executed by the one or more processors, the one or more processors implement the method described in the present disclosure.

According to another aspect of the present disclosure, a computer-readable storage medium is provided, on which executable instructions are stored. When the executable instructions are executed by a processor, the processor implements the method described in the present disclosure.

According to another aspect of the present disclosure, a computer program product is provided. The computer program product includes computer executable instructions. When the computer executable instructions are executed, they are used to implement the method described in the present disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other objects, features and advantages of the present disclosure will become more apparent through the following description of the embodiments of the present disclosure with reference to the accompanying drawings, in which:

FIG1 schematically shows a system architecture to which a method for processing a gateway service request and a method for managing a cloud-native gateway system can be applied according to an embodiment of the present disclosure;

FIG2 schematically shows a flow chart of a method for processing a gateway service request according to an embodiment of the present disclosure;

3 schematically shows an example schematic diagram of determining target gateway cluster information corresponding to a target gateway cluster, target gateway information corresponding to a target gateway, and target service information corresponding to a target service according to a preset mapping relationship and the to-be-processed gateway service configuration information in the to-be-processed service request according to an embodiment of the present disclosure;

FIG4 schematically shows an example schematic diagram of constructing a second key-value relationship according to an embodiment of the present disclosure;

5A schematically shows an example schematic diagram of determining gateway address information corresponding to a gateway identifier according to a target routing protocol and virtual network address information according to an embodiment of the present disclosure;

5B schematically shows an example schematic diagram of determining gateway address information corresponding to a gateway identifier according to a target routing protocol and virtual network address information according to another embodiment of the present disclosure;

FIG6 schematically shows an example schematic diagram of constructing a third key-value relationship according to an embodiment of the present disclosure;

7 schematically shows an example schematic diagram of determining the respective running states of at least one container group corresponding to a target service according to target gateway cluster information, target gateway information and target service information according to an embodiment of the present disclosure;

FIG8 schematically shows an example schematic diagram of a method for processing a gateway service request according to an embodiment of the present disclosure;

FIG9 schematically shows an example schematic diagram of a method for managing a cloud native gateway system according to an embodiment of the present disclosure;

FIG10 schematically shows a block diagram of a device for processing a service request according to an embodiment of the present disclosure;

FIG. 11 schematically shows a management device of a cloud native gateway system according to an embodiment of the present disclosure. Example schematic diagram of the configuration; and

Figure 12 schematically shows a block diagram of an electronic device suitable for implementing a method for processing gateway service requests and a method for managing a cloud-native gateway system according to an embodiment of the present disclosure.

DETAILED DESCRIPTION

Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the present disclosure. In the following detailed description, for ease of explanation, many specific details are set forth to provide a comprehensive understanding of the embodiments of the present disclosure. However, it is apparent that one or more embodiments may also be implemented without these specific details. In addition, in the following description, descriptions of known structures and technologies are omitted to avoid unnecessary confusion of the concepts of the present disclosure.

The terms used herein are only for describing specific embodiments and are not intended to limit the present disclosure. The terms "include", "comprising", etc. used herein indicate the existence of the features, steps, operations and/or components, but do not exclude the existence or addition of one or more other features, steps, operations or components.

All terms (including technical and scientific terms) used herein have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein should be interpreted as having a meaning consistent with the context of this specification, and should not be interpreted in an idealized or overly rigid manner.

In the case of using expressions such as "at least one of A, B, and C, etc.", it should generally be interpreted in accordance with the meaning of the expression generally understood by those skilled in the art (for example, "a system having at least one of A, B, and C" should include but is not limited to a system having A alone, B alone, C alone, A and B, A and C, B and C, and/or A, B, C, etc.). In the case of using expressions such as "at least one of A, B, or C, etc.", it should generally be interpreted in accordance with the meaning of the expression generally understood by those skilled in the art (for example, "a system having at least one of A, B, or C" should include but is not limited to a system having A alone, B alone, C alone, A and B, A and C, B and C, and/or A, B, C, etc.).

In the embodiments of the present disclosure, the collection, updating, analysis, processing, use, transmission, provision, disclosure, storage, etc. of the data involved (for example, including but not limited to user personal information) are in compliance with the provisions of relevant laws and regulations, are used for legitimate purposes, and do not violate public order and good morals. In particular, necessary measures are taken for user personal information to prevent illegal access to user personal information data and maintain the security of user personal information, network security, and national security.

In the embodiments of the present disclosure, the user's authorization or consent is obtained before obtaining or collecting the user's personal information.

For example, after collecting the gateway service configuration information to be processed, the user information can be desensitized by using methods including de-identification or anonymization to protect the security of user information.

The API gateway can receive client requests, forward the requests to the corresponding backend system services according to predetermined policies and routes, and process the results returned by the backend servers.

The resources in the Ingress API resource collection and the gateway API resource collection can work together to build models for various network use cases. The gateway API resource collection can include at least one of the following: gatewayclass resources, gateway resources, HTTPRoute resources, TCPRoute resources, and Service resources. The gateway API can achieve configuration decoupling by separating resource objects so that resources can be managed by people with different roles.

However, since there are fewer attributes in the Ingress gateway definition, for host domain name, path path, port port, etc., header rewriting, hosts rewriting, weight and other functions need to be added through annotations in the Ingress gateway definition, resulting in a poor user experience. In addition, since the current gateway definition only formulates specifications, the gatewayController that actually takes charge of issuing routing rules has not been implemented.

In summary, in the process of implementing the concept of the present disclosure, the inventors found that there are at least the following problems in the related art: the high availability of resources and services in Kubernetes cannot be guaranteed.

In order to at least partially solve the technical problems existing in the related technologies, the present disclosure provides a method for processing a gateway service request, a method and device for managing a cloud native gateway system, which can be applied to the fields of network technology and cloud native technology. The method for processing a gateway service request includes: in response to receiving a pending gateway service request, determining the target gateway cluster information corresponding to the target gateway cluster, the target gateway information corresponding to the target gateway, and the target gateway information corresponding to the target service according to the preset mapping relationship and the pending gateway service configuration information in the pending gateway service request. The target service information is obtained; according to the target gateway cluster information, the target gateway information and the target service information, the operating status of at least one container group corresponding to the target service is determined; according to the operating status of at least one container group corresponding to the target service, the target container group is determined in the at least one container group; the to-be-processed gateway service request is sent to the target container group, so that the target container group processes the to-be-processed gateway service request.

It should be noted that the method for processing gateway service requests, the method for managing a cloud native gateway system, and the device provided in the embodiments of the present disclosure can be used in the field of network technology and the field of cloud native technology, for example, in the field of container technology. The method for processing gateway service requests, the method for managing a cloud native gateway system, and the device provided in the embodiments of the present disclosure can also be used in any field other than the field of network technology and the field of cloud native technology, for example, in the field of information processing technology. The application field of the method for processing gateway service requests, the method for managing a cloud native gateway system, and the device provided in the embodiments of the present disclosure is not limited.

FIG1 schematically shows a system architecture to which a method for processing a gateway service request and a method for managing a cloud native gateway system can be applied according to an embodiment of the present disclosure. It should be noted that FIG1 is only an example of a system architecture to which an embodiment of the present disclosure can be applied, to help those skilled in the art understand the technical content of the present disclosure, but does not mean that the embodiment of the present disclosure cannot be used in other devices, systems, environments or scenarios.

As shown in FIG1 , the system architecture 100 according to this embodiment may include a first terminal device 101, a second terminal device 102, a third terminal device 103, a network 104, and a server 105. The network 104 is used to provide a medium for a communication link between the first terminal device 101, the second terminal device 102, the third terminal device 103, and the server 105. The network 104 may include various connection types, such as wired, wireless communication links, or optical fiber cables, etc.

The user may use at least one of the first terminal device 101, the second terminal device 102, and the third terminal device 103 to interact with the server 105 through the network 104 to receive or send messages, etc. Various communication client applications may be installed on the first terminal device 101, the second terminal device 102, and the third terminal device 103, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (only for example).

The first terminal device 101, the second terminal device 102, and the third terminal device 103 can be various electronic devices with display screens and supporting web browsing, including but not limited to smart phones, Tablets, laptops, desktops, and more.

The server 105 may be a server that provides various services, such as a background management server (only as an example) that provides support for websites browsed by users using the first terminal device 101, the second terminal device 102, and the third terminal device 103. The background management server may analyze and process the received data such as user requests, and feed back the processing results (such as web pages, information, or data obtained or generated according to user requests) to the terminal device.

It should be noted that the method for processing the gateway service request and the method for managing the cloud native gateway system provided in the embodiment of the present disclosure can generally be executed by the server 105. Accordingly, the processing device for the gateway service request and the management device for the cloud native gateway system provided in the embodiment of the present disclosure can generally be set in the server 105. The method for processing the gateway service request and the management method for the cloud native gateway system provided in the embodiment of the present disclosure can also be executed by a server or server cluster that is different from the server 105 and can communicate with the first terminal device 101, the second terminal device 102, the third terminal device 103 and/or the server 105. Accordingly, the processing device for the gateway service request and the management device for the cloud native gateway system provided in the embodiment of the present disclosure can also be set in a server or server cluster that is different from the server 105 and can communicate with the first terminal device 101, the second terminal device 102, the third terminal device 103 and/or the server 105.

Alternatively, the method for processing a gateway service request and the method for managing a cloud-native gateway system provided in the embodiments of the present disclosure may also be executed by the first terminal device 101, the second terminal device 102, or the third terminal device 103, or may also be executed by other terminal devices different from the first terminal device 101, the second terminal device 102, or the third terminal device 103. Accordingly, the device for processing a gateway service request and the device for managing a cloud-native gateway system provided in the embodiments of the present disclosure may also be provided in the first terminal device 101, the second terminal device 102, or the third terminal device 103, or in other terminal devices different from the first terminal device 101, the second terminal device 102, or the third terminal device 103.

It should be understood that the number of terminal devices, networks and servers in Figure 1 is only illustrative. Any number of terminal devices, networks and servers may be provided according to implementation requirements.

It should be noted that the sequence numbers of the operations in the following method are only used as representations of the operations for the purpose of description, and should not be regarded as representing the execution order of the operations. Unless explicitly stated, the method does not need to be executed completely in the order shown.

FIG2 schematically shows a flow chart of a method for processing a gateway service request according to an embodiment of the present disclosure.

As shown in FIG. 2 , the gateway service request processing method 200 includes operations S210 to S240 .

In operation S210, in response to receiving a pending gateway service request, target gateway cluster information corresponding to the target gateway cluster, target gateway information corresponding to the target gateway, and target service information corresponding to the target service are determined according to a preset mapping relationship and the pending gateway service configuration information in the pending gateway service request.

In operation S220, the operating state of each of at least one container group corresponding to the target service is determined according to the target gateway cluster information, the target gateway information, and the target service information.

In operation S230, a target container group is determined in the at least one container group according to the respective running states of the at least one container group corresponding to the target service.

In operation S240 , the to-be-processed gateway service request is sent to the target container group, so that the target container group processes the to-be-processed gateway service request.

According to an embodiment of the present disclosure, a method for processing a gateway service request can be implemented based on the container orchestration engine Kubernetes. In Kubernetes, multiple containers can be created, an application instance can be run in each container, and the application instance can be managed and accessed through the built-in strategy. For example, a service in Kubernetes can be exposed to the outside of the cluster or a request outside the cluster can be forwarded to the inside of the cluster through a gateway proxy for access by clients outside the cluster.

According to an embodiment of the present disclosure, the method of implementing the interaction between Kubernetes and the client may include at least one of the following: a method based on Ingress and Ingress Controller, and a method based on gateway and gatewayController. Ingress and gateway may refer to routing rules customized by the client. IngressController and gatewayController may be provided by software vendors, and may dynamically perceive changes in routing rules in the cluster through interaction with Kubernetes.

According to an embodiment of the present disclosure, a code for generating a pending gateway service request may be pre-written into a target script. In response to detecting a gateway service processing operation initiated by a target user using a target terminal, the target terminal may run the target script to generate a pending gateway service request message and send the message to a server, so that the server can process the pending gateway service request. Service request message for processing.

According to an embodiment of the present disclosure, the preset mapping relationship may include at least one of the following: a preset mapping relationship between virtual Internet Protocol address (VIP) information and gateway cluster information, a preset mapping relationship between gateway address information and gateway information, and a preset mapping relationship between service port information and service information.

According to an embodiment of the present disclosure, gateway cluster information can be used to describe different gateway clusters. The gateway cluster information can include at least one of a gateway cluster identifier and a gateway cluster name. For example, the virtual Internet Protocol address information matching the service configuration information to be processed can be determined based on a preset mapping relationship between the virtual Internet Protocol address information and the gateway cluster information. In this case, the gateway cluster information corresponding to the virtual Internet Protocol address information can be determined as the target gateway cluster information.

According to an embodiment of the present disclosure, a gateway cluster may include at least one gateway. At least one gateway may each correspond to gateway address information. For example, the gateway may refer to an API gateway (i.e., Application Programming Interface, application program interface gateway). The gateway may include at least one of the following: Spring Cloud Gateway gateway and Nginx gateway. The gateway may route according to the request received from the client so as to forward the request to the corresponding backend service. In addition, the gateway may route according to the data received from the backend service so as to forward the data to the corresponding client.

According to an embodiment of the present disclosure, gateway information can be used to describe different gateways. Gateway information can include at least one of a gateway identifier and a gateway name. For example, gateway address information matching the service configuration information to be processed can be determined based on a preset mapping relationship between gateway address information and gateway information. In this case, gateway information corresponding to the gateway address information can be determined as target gateway information.

According to an embodiment of the present disclosure, each of the at least one gateway may correspond to at least one service. At least one service may correspond to service port information. The service information may be used to describe different services. The service information may include at least one of a service identifier and a service name. For example, the service port information matching the service configuration information to be processed may be determined based on a preset mapping relationship between the service port information and the service information. In this case, the service information corresponding to the service port information may be determined as the target service. information.

According to an embodiment of the present disclosure, each service in at least one service may correspond to at least one container group (i.e., pod). A container group may represent the smallest deployable computing unit created and managed in a container cluster. Each container group in at least one container group may include at least one container. At least one container group may correspond to container group address information. After obtaining the target gateway cluster information, the target gateway information, and the target service information, the operating status of at least one container group may be determined according to the container group address information of at least one container group corresponding to the target service. The operating status may be used to characterize whether the container group is running normally.

According to an embodiment of the present disclosure, after obtaining the respective operating status of at least one container group corresponding to the target service, a target container group can be determined in the at least one container group according to the respective operating status of the at least one container group. For example, a container group whose operating status indicates normal operation can be determined as the target container group.

According to an embodiment of the present disclosure, after determining the target container group, the to-be-processed gateway service request can be sent to the target container group according to the container group address information corresponding to the target container group, so that the target container group processes the to-be-processed gateway service request and returns a processing result message.

According to the embodiments of the present disclosure, since the target container group is determined according to the respective operating states of at least one container group corresponding to the target service, and the operating state is determined according to the target gateway cluster information, the target gateway information and the target service information, it is possible to determine the target container group whose operating state is normal operation. On this basis, by sending the pending gateway service request to the target container group, automatic routing of the gateway service request is achieved, and by using the target container group to process the pending gateway service request, automatic processing of the gateway service request is achieved, thereby at least partially overcoming the technical problem in the related art that the high availability of resources and services in Kubernetes cannot be guaranteed, and improving the stability of request processing, thereby ensuring the high availability of resources and services.

The method 200 for processing a gateway service request according to an embodiment of the present disclosure will be further described below with reference to FIGS. 3 , 4 , 5A, 5B, 6 , 7 and 8 .

According to an embodiment of the present disclosure, the gateway service request processing method 200 may be based on The gatewayController is implemented by gatewayController. The gatewayController can monitor the update events of the gateway, assign a virtual Internet Protocol address to the gateway, and store the gateway monitoring content to the distributed registration service center (such as ETCD). In addition, the gatewayController can monitor the domain name, path, request parameter rewrite, backend and weight on the httproute, and store the httproute monitoring content to the distributed registration service center.

According to the embodiments of the present disclosure, based on the native semantics of the v1beta version of the gateway, the code logic of the gatewayController is formed by expanding and supplementing the k8s-gateway standard, thereby realizing the gateway control plane service. By using the front-end agent to dynamically add and delete the open source gateway listening port, the data plane service is realized. On this basis, the scheduling of VIP is completed through the cooperation of the gatewayController and the front-end agent, thereby forming a complete cloud-native seven-layer gateway service. This will be explained below according to specific embodiments.

According to an embodiment of the present disclosure, operation S210 may include the following operations.

Determine the target virtual Internet Protocol address information according to the gateway service configuration information to be processed. Determine the target gateway cluster information corresponding to the target gateway cluster according to the first preset mapping relationship and the target virtual Internet Protocol address information. Determine the gateway address information corresponding to the target gateway and the service port information corresponding to the target service according to the target gateway cluster information. Determine the target gateway information according to the second preset mapping relationship and the gateway address information. Determine the target service information according to the third preset mapping relationship and the service port information.

According to an embodiment of the present disclosure, a gateway cluster, a gateway, and a service may belong to a custom resource (Custom Resource Definition, CRD). After obtaining the configuration information of the gateway service to be processed, the configuration information of the gateway service to be processed may be processed to obtain a processing result. According to the processing result, the target virtual network address information is determined. The target virtual network address information may be used to indicate the target gateway cluster. The processing method of the service configuration information to be processed may be configured according to actual business needs and is not limited here. For example, the service configuration information to be processed may be parsed to obtain the domain name information corresponding to the service request to be processed. On this basis, the target virtual network address information is determined according to the domain name information.

According to an embodiment of the present disclosure, the first preset mapping relationship can be used to characterize the preset mapping relationship between the virtual Internet Protocol address information and the gateway cluster information. The relationship may include at least one first key-value relationship. The first key-value relationship may be created based on the virtual Internet Protocol address information and the gateway cluster information. The first key-value relationship may include a one-to-one correspondence between the virtual Internet Protocol address information and the gateway cluster information. The gateway cluster may be represented by a gatewayclass. A gatewayclass may refer to a group of gateways with common configurations and behaviors. A gateway cluster may be used to describe the definition of different gateway services by k8s operation and maintenance, and to selectively authorize a gateway cluster that meets the business scenario to the business operation and maintenance.

According to an embodiment of the present disclosure, a second preset mapping relationship can be used to characterize a preset mapping relationship between gateway address information and gateway information. A gateway can be characterized by a gateway. A gateway can refer to a point that can convert traffic to a service within a cluster. A gateway can be used to describe the business operation and maintenance definition of the scope of use of a gateway, for example, by which services under which namespace can use it. In addition, a gateway has a VIP and a listening port, and business operation and maintenance can authorize business users who meet the scope of use through a gateway.

According to an embodiment of the present disclosure, the third preset mapping relationship can be used to characterize the preset mapping relationship between the service port information and the service information. The route can be characterized by httproute. httproute can refer to how the traffic obtained through the gateway is mapped to the service. httproute can be used to describe the matching rule description of the business user for the business service. For example, the domain name, path and backend can be bound to the gateway to realize external exposure of the service.

According to the embodiments of the present disclosure, since the target gateway cluster information is determined based on the first preset mapping relationship and the target virtual Internet Protocol address information, the target gateway information is determined based on the second preset mapping relationship and the gateway address information, and the target service information is determined based on the third preset mapping relationship and the service port information, it is possible to automatically determine the target gateway cluster information, target gateway information and target service information based on the gateway service configuration information to be processed, thereby improving the efficiency of information processing and thereby improving the efficiency of processing gateway service requests.

Figure 3 schematically shows an example schematic diagram of determining the target gateway cluster information corresponding to the target gateway cluster, the target gateway information corresponding to the target gateway, and the target service information corresponding to the target service according to a preset mapping relationship and the pending gateway service configuration information in the pending gateway service request according to an embodiment of the present disclosure.

As shown in FIG. 3 , in 300 , at least one gateway cluster includes a gateway cluster 304_1 and a gateway cluster 304_2, and at least one gateway corresponding to the gateway cluster 304_1 includes a gateway 304_11 and gateway 304_12, at least one service corresponding to gateway 304_11 includes service 304_111, at least one service corresponding to gateway 304_12 includes service 304_121 and service 304_122, at least one gateway corresponding to gateway cluster 304_2 includes gateway 304_21 and gateway 304_22, at least one service corresponding to gateway 304_21 includes service 304_211, service 304_212 and service 304_213, and at least one service corresponding to gateway 304_22 includes service 304_221 as an example to illustrate the information determination method of an embodiment of the present disclosure.

In response to receiving the pending gateway service request 301, the target virtual Internet Protocol address information 302 can be determined according to the pending gateway service configuration information 301_1 in the pending gateway service request 301. According to the target virtual Internet Protocol address information 302 and the first preset mapping relationship, the target gateway cluster information corresponding to the gateway cluster 304_2 is determined. According to the target gateway cluster information corresponding to the gateway cluster 304_2, the gateway address information 305 and the service port information 307 can be determined. According to the gateway address information 305 and the second preset mapping relationship 306, the target gateway information corresponding to the gateway 304_21 can be determined. According to the service port information 307 and the third preset mapping relationship 308, the target service information corresponding to the service 304_212 can be determined.

According to an embodiment of the present disclosure, determining target virtual Internet Protocol address information according to the to-be-processed gateway service configuration information may include the following operations.

In response to receiving the pending gateway service request, the pending gateway service configuration information is parsed to obtain domain name information corresponding to the pending gateway service request, and the target virtual network address information is determined according to the domain name information.

According to an embodiment of the present disclosure, domain name information may refer to the name of a computer or computer group on the Internet consisting of a string of names separated by dots. Domain name information may be used to identify the electronic location of a computer during data transmission.

According to the embodiments of the present disclosure, after obtaining the domain name information, the domain name information can be further subjected to domain name resolution processing to map the domain name information into an IP address and obtain the target virtual network address information. The domain name resolution processing method can be configured according to actual business needs and is not limited here. For example, the domain name resolution processing method can include at least one of the following: recursive resolution and iterative resolution. Recursive resolution can refer to completing the transformation of a name and an address at one time. Iterative resolution can refer to requesting a single server each time.

According to an embodiment of the present disclosure, at least one second key-value relationship may be: The formula is constructed.

For each second key-value relationship in at least one second key-value relationship, in response to receiving a gateway creation instruction, a gateway identifier, gateway configuration information, and a gateway cluster identifier are obtained. According to the gateway cluster identifier, virtual network address information corresponding to the gateway cluster identifier is determined. According to the target routing protocol and the virtual network address information, the gateway address information corresponding to the gateway identifier is determined. The gateway address information is determined as the second key information. The gateway configuration information is determined as the second value information. A second key-value relationship is constructed according to the second key information and the second value information.

According to an embodiment of the present disclosure, the second preset mapping relationship may include at least one second key-value relationship. The second key-value relationship may include second key information and second value information.

According to an embodiment of the present disclosure, the Kubernetes cluster can obtain the newly created gateway configuration information when monitoring the existence of a newly created gateway, and generate a gateway creation instruction based on the information. The gateway configuration information may include at least one of the following: a gateway identifier and a gateway cluster identifier.

According to an embodiment of the present disclosure, the code for generating a gateway creation instruction can be pre-written into a first script. In response to detecting a gateway creation operation initiated by a target user using a target terminal, the target terminal can run the first script, generate a gateway creation instruction message and send the message to the server, so that the server can create a gateway according to the message.

According to an embodiment of the present disclosure, a target routing protocol can be used to implement conversion between private IP addresses and public IP addresses to access the Internet. A private IP address can refer to an address used in a local area network. A public IP address can refer to an address that can be directly accessed on the Internet.

According to the embodiments of the present disclosure, the target routing protocol can be configured according to actual business needs, which is not limited here. For example, the target routing protocol can include at least one of the following: ALL-IN mode routing protocol, Equal Cost Multi Path (ECMP), Border Gateway Protocol (BGP), and Open Shortest Path First (OSPF).

According to an embodiment of the present disclosure, the gateway address information corresponding to the gateway identifier can be determined according to the target routing protocol and the virtual network address information. After obtaining the virtual network address information and the gateway address information, the gateway address information and the gateway configuration information can be used to create a gateway address. Second key-value relationship: The second key-value relationship may include a one-to-one correspondence between gateway address information and gateway configuration information.

According to an embodiment of the present disclosure, in this case, determining the target gateway information according to the second preset mapping relationship and the gateway address information may include: determining at least one first similarity according to the gateway address information and the second key information corresponding to each of the at least one second key-value relationships. Determining the target second key information according to the at least one first similarity. Determining the target second value information corresponding to the target second value information according to the target second key information. Determining the target gateway information according to the gateway configuration information corresponding to the target second value information.

According to an embodiment of the present disclosure, since the second preset mapping relationship may include at least one second key-value relationship, and the second key-value relationship is determined in response to receiving a gateway creation instruction, the second key-value relationship may include a one-to-one correspondence between gateway address information and gateway configuration information, which is beneficial for the subsequent use of the second preset mapping relationship to automatically determine the target gateway information, thereby improving the efficiency of determining the target gateway information, and further improving the efficiency of processing gateway service requests.

FIG. 4 schematically shows an example schematic diagram of constructing a second key-value relationship according to an embodiment of the present disclosure.

As shown in FIG. 4 , in 400 , in response to receiving a gateway creation instruction 401 , gateway configuration information 401_1 , a gateway cluster identifier 401_2 , and a gateway identifier 401_3 may be acquired.

The virtual network address information 402 corresponding to the gateway cluster identification 401_2 can be determined according to the gateway cluster identification 401_2. After the virtual network address information 402 is obtained, the gateway address information 404 corresponding to the gateway identification 401_3 can be determined according to the target routing protocol 403 and the virtual network address information 402.

After obtaining the gateway address information 404, the gateway address information 404 may be determined as the second key information 405. The gateway configuration information 401_1 may be determined as the second value information 406. According to the second key information 405 and the second value information 406, a second key-value relationship 407 may be constructed.

According to an embodiment of the present disclosure, when the target routing protocol is the Border Gateway Protocol, determining the gateway address information corresponding to the gateway identifier according to the target routing protocol and the virtual network address information may include the following operations.

According to the virtual Internet Protocol address information, a first resource pool is configured, wherein the first resource The source pool includes at least one first candidate address information. According to the first resource pool, the target address information is determined in the at least one first candidate address information. According to the border gateway protocol, the target address information is published via any two front-end agents so as to determine the target address information as the gateway address information.

According to an embodiment of the present disclosure, the border gateway protocol may refer to a dynamic routing protocol used to exchange routing information between different autonomous systems (Autonomous System, AS) or within the same autonomous system. For example, when two autonomous systems need to exchange routing information, a node running the border gateway protocol may be designated for each autonomous system, and the node represents the autonomous system to exchange routing information with other autonomous systems.

According to an embodiment of the present disclosure, a node running a border gateway protocol may include at least one of a host and a router. Taking a router as an example, after the router receives routing information from an upstream neighbor, the best route in the dynamic routing protocol learned by the device can be flushed to the driver to guide traffic forwarding, and the best route in the dynamic routing protocol learned by the device can be notified to the neighbor.

According to an embodiment of the present disclosure, the first resource pool may include at least one first candidate address information. The first candidate address information may refer to a VIP address. At least one first candidate address information may be managed and scheduled by a gatewayContrller. The first resource pool may include at least one of the following: a first dynamic resource pool (i.e., Dynamic Pool) and a first static resource pool (i.e., Static Pool).

According to an embodiment of the present disclosure, after receiving a gateway creation instruction, a corresponding first resource pool can be configured for the terminal according to the virtual Internet Protocol address information. After the first resource pool is determined, the target address information can be determined from at least one first candidate address information, and the target address information can be returned to the gateway. In addition, the task of publishing the gateway address information corresponding to the gateway can be notified to any two front-end agents (i.e., agents), and the target address information can be published to the switch based on the border gateway protocol via the any two front-end agents, and the target address information can be bound to the local loopback interface. The nodes of any two front-end agents can be set according to actual business needs, and are not limited here. It is only necessary to ensure that there are an even number of nodes. For example, it can be the 2nth node and the 2n+1th node.

According to an embodiment of the present disclosure, the front-end proxy can be used with an open source gateway (such as Apisix) Deployed in the same container, multiple copies are deployed through k8s statefulset. The network mode uses host mode. Other containers can be excluded through k8s taints and anti-affinity to achieve exclusive nodes. Multi-copy deployment can refer to the selection of the master through the k8s lease, that is, only the master node is responsible for listening to events and reading and writing distributed registration service centers. The front-end proxy can reload the listening port to the open source gateway, so that the front-end proxy can dynamically add and delete the open source gateway listening port.

According to an embodiment of the present disclosure, the gatewayController can cooperate with the front-end agent to complete the scheduling of VIP. For example, the PodIP and PodName can be mapped to the environment variables of the container through the k8s downwardAPI. The front-end agent can intercept the serial number from the PodName and report its own heartbeat and serial number to the gatewayController. The gatewayController can perform bit operations on the VIP to obtain the decimal sum of the 4-segment IP, and then perform modulus operations on the number of Apisix nodes to obtain the corresponding node. The gatewayController can write the VIP into the distributed registration service center directory of the corresponding node to complete the scheduling of the VIP.

According to the embodiments of the present disclosure, since the target address information is determined in at least one first candidate address information according to the first resource pool, the target address information is automatically determined, thereby shortening the VIP address scheduling time, improving the processing efficiency of the VIP address scheduling, and further improving the efficiency of determining the gateway address information. On this basis, since the gateway address information is determined according to the border gateway protocol through any two front-end agents publishing the target address information, optimization of operation and maintenance and business users is achieved.

FIG. 5A schematically shows an example schematic diagram of determining gateway address information corresponding to a gateway identifier according to a target routing protocol and virtual network address information according to an embodiment of the present disclosure.

As shown in FIG. 5A, in 500A, a first resource pool 502 may be configured according to virtual Internet Protocol address information 501. The first resource pool 502 may include at least one first candidate address information. The at least one first candidate address information may include first candidate address information 502_1, first candidate address information 502_2, ..., first candidate address information 502_p, ..., first candidate address information 502_P. P may be an integer greater than or equal to 1, p∈{1, 2, ..., (P-1), P}.

The first candidate address information 502_1, the first candidate address information 502_2, ..., The target address information 503 is determined from the first candidate address information 502_p, ..., and the first candidate address information 502_P. According to the border gateway protocol 504, the target address information 503 is published via the front-end proxy 505_1 and the front-end proxy 505_2, so that the target address information 503 is determined as the gateway address information 506.

According to an embodiment of the present disclosure, when the target routing protocol is an equal-cost multi-path routing protocol, determining the gateway address information corresponding to the gateway identifier according to the target routing protocol and the virtual network address information may include the following operations.

According to the virtual Internet Protocol address information, a second resource pool is configured, wherein the second resource pool includes at least one second candidate address information. According to the second resource pool, target address information is determined in the at least one second candidate address information. According to the equal-cost multi-path routing protocol, equal-cost routing information corresponding to the target address information is configured. The equal-cost routing information is determined as the gateway address information.

According to an embodiment of the present disclosure, an equal-cost multi-path routing protocol may refer to using multiple links simultaneously in any network environment, that is, a network environment in which multiple different links exist to reach the same destination address. The path selection method of the equal-cost multi-path routing protocol may be set according to actual business needs and is not limited here. For example, the path selection method may include at least one of the following: a hash-based path selection method, a polling-based path selection method, and a path weight-based path selection method.

According to an embodiment of the present disclosure, the second resource pool may include at least one second candidate address information. The second candidate address information may refer to a VIP address. At least one second candidate address information may be managed and scheduled by a gatewayContrller. The second resource pool may include at least one of the following: a second dynamic resource pool (i.e., Dynamic Pool) and a second static resource pool (i.e., Static Pool).

According to an embodiment of the present disclosure, the VIP network segment can be equally routed to all nodes of apisix by configuring equal-cost routing on the switch. After receiving the gateway creation instruction, the corresponding second resource pool can be configured for the terminal according to the virtual Internet Protocol address information. After the second resource pool is determined, the target address information can be determined from at least one second candidate address information, and the equivalent routing information corresponding to the target address information can be configured via the equal-cost multipath routing protocol, and the equivalent routing information is returned to the gateway.

According to the embodiment of the present disclosure, when the target routing protocol is an ALL-IN mode routing protocol, all the apisix node IPs reported by the front-end agent can be returned to the gateway, and the service user can select one or more IP gateway address information by himself. The specific implementation in this case is relatively simple.

According to the embodiments of the present disclosure, since the target address information is determined in at least one second candidate address information according to the second resource pool, the target address information is automatically determined, thereby shortening the VIP address scheduling time, improving the processing efficiency of VIP address scheduling, and further improving the efficiency of determining the gateway address information. On this basis, since the gateway address information is determined according to the equal-cost multi-path routing protocol by configuring the equal-cost routing information corresponding to the target address information, it is more friendly to business users and improves the user experience.

FIG5B schematically shows an example schematic diagram of determining gateway address information corresponding to a gateway identifier according to a target routing protocol and virtual network address information according to another embodiment of the present disclosure.

As shown in FIG. 5B , in 500B, a second resource pool 508 may be configured according to the virtual Internet Protocol address information 507. The second resource pool 508 may include at least one second candidate address information. The at least one second candidate address information may include second candidate address information 508_1, second candidate address information 508_2, ..., second candidate address information 508_q, ..., second candidate address information 508_Q. Q may be an integer greater than or equal to 1, q∈{1, 2, ..., (Q-1), Q}.

The target address information 509 can be determined from the second candidate address information 508_1, the second candidate address information 508_2, ..., the second candidate address information 508_q, ..., the second candidate address information 508_Q. According to the equal-cost multi-path routing protocol 510, the equal-cost routing information 511 corresponding to the target address information 509 is configured. The equal-cost routing information 511 is determined as the gateway address information 512.

According to an embodiment of the present disclosure, determining the gateway address information corresponding to the target gateway and the service port information corresponding to the target service according to the target gateway cluster information may include the following operations.

Determine the network segment range of the target gateway cluster based on the target gateway cluster information. For each of the at least one gateway, determine the gateway address information corresponding to the gateway according to the network segment range of the target gateway cluster. For each of the at least one service corresponding to the gateway, determine the service port information of the service corresponding to the gateway according to the gateway address information corresponding to the gateway.

According to an embodiment of the present disclosure, the target gateway cluster may include at least one gateway. Each of the at least one gateway may correspond to at least one service. The at least one gateway may correspond to gateway address information. The at least one service may correspond to service port information.

According to an embodiment of the present disclosure, after obtaining the target gateway cluster information, the network segment range of the target gateway cluster can be determined according to the target gateway cluster information. The network segment range can be characterized by W.X.Y.Z. W, X, Y, Z∈[0, 255]. For example, the network segment range can be set to W∈[0, 10], X∈[0, 10], ∈[0, 10], Z∈[0, 255], that is, the network segment range may include an Internet Protocol address in the range of 0.0.0.0 to 10.10.10.255. After obtaining the network segment range of the target gateway cluster, the gateway address information corresponding to the gateway can be determined for each gateway in at least one gateway.

According to an embodiment of the present disclosure, at least one third key-value relationship may be constructed in the following manner.

For each third key-value relationship in at least one third key-value relationship, in response to receiving a service creation instruction, obtain a service identifier, service configuration information, and a gateway identifier. According to the gateway identifier, determine the gateway address information corresponding to the gateway identifier. According to the gateway address information, determine the service port information corresponding to the service identifier. Determine the service port information as the third key information. Determine the service configuration information as the third value information. Construct a third key-value relationship according to the third key information and the third value information.

According to an embodiment of the present disclosure, the third preset mapping relationship may include at least one third key-value relationship. The third key-value relationship may include third key information and third value information.

According to an embodiment of the present disclosure, the Kubernetes cluster can obtain the newly created service configuration information when monitoring the existence of a newly created service, and generate a service creation instruction based on this. The service configuration information may include at least one of the following: container address, service domain name, service port, and service annotation information.

According to an embodiment of the present disclosure, the code for generating a service creation instruction can be pre-written into a second script. In response to detecting a service creation operation initiated by a target user using a target terminal, the target terminal can run the second script, generate a service creation instruction message and send the message to the server, so that the server can create a service based on the message.

According to an embodiment of the present disclosure, the gateway address information corresponding to the gateway identifier can be determined according to the gateway identifier. The service port information corresponding to the service identifier can be determined according to the gateway address information. After obtaining the service port information, a third key value relationship can be created according to the service port information and the service configuration information. The third key value relationship may include a one-to-one correspondence between the service port information and the service configuration information.

According to an embodiment of the present disclosure, in this case, determining the target service information according to the third preset mapping relationship and the service port information may include: determining at least one second similarity according to the service port information and the third key information corresponding to each of the at least one third key-value relationships. Determining the target third key information according to the at least one second similarity. Determining the target third value information corresponding to the target third value information according to the target third key information. Determining the target service information according to the service configuration information corresponding to the target third value information.

According to an embodiment of the present disclosure, since the third preset mapping relationship may include at least one third key-value relationship, and the third key-value relationship is determined in response to receiving a service creation instruction, the third key-value relationship may include a one-to-one correspondence between service port information and service configuration information, which is beneficial for the subsequent use of the third preset mapping relationship to automatically determine the target service information, thereby improving the efficiency of determining the target service information, and further improving the efficiency of processing service requests.

FIG. 6 schematically shows an example schematic diagram of constructing a third key-value relationship according to an embodiment of the present disclosure.

As shown in FIG. 6 , in 600 , in response to receiving a service creation instruction 601 , gateway service configuration information 601_1 , a gateway identifier 601_2 , and a service identifier 601_3 may be acquired.

According to the gateway identifier 601_2, the gateway address information 602 corresponding to the gateway identifier 601_2 can be determined. According to the gateway address information 602, the service port information 603 corresponding to the service identifier 601_3 can be determined.

The service port information 603 can be determined as the third key information 604. The configuration information 6011 is determined as the third value information 605. According to the third key information 604 and the third value information 605, a third key-value relationship 606 is constructed.

According to an embodiment of the present disclosure, operation S220 may include the following operations.

For each container group address information in the at least one container group address information, a detection network connection is established with the container group according to the container group address information. If a heartbeat detection packet sent by the container group is received within a predetermined period of time, it is determined that the running state of the container group is a normal running state. If a heartbeat detection packet sent by the container group is not received within the predetermined period of time, it is determined that the running state of the container group is an abnormal running state.

According to an embodiment of the present disclosure, the target service information may include container group address information corresponding to each of the at least one container groups.

According to an embodiment of the present disclosure, the detection network connection can be used to characterize a short connection between a gatewayContrller and a container group. A short connection can mean that during data transmission, a connection is established only when data needs to be sent, and the connection is disconnected after the data is sent, that is, each connection only completes the sending of one service. After the detection network connection is established, a heartbeat detection packet can be sent to the container group based on the detection network connection.

According to an embodiment of the present disclosure, a heartbeat detection packet may refer to a custom command word that periodically notifies each other of the status of the gatewayContrller and the container group, and the heartbeat detection packet may be sent at a predetermined time interval. The predetermined time period may be set according to actual business needs and is not limited here. The predetermined time period may be a pre-set detection time interval, for example, the predetermined time period may be set to 30 minutes.

According to an embodiment of the present disclosure, operation S230 may include the following operations.

In response to the running state of the container group being a normal running state, the container group is determined as a target container group.

According to an embodiment of the present disclosure, the abnormal operation state may be determined when a heartbeat detection packet sent by the container group is not received within a predetermined period of time. The normal operation state may be determined when a heartbeat detection packet sent by the container group is received within a predetermined period of time. The container group whose operation state is the normal operation state may be determined as the target container group.

FIG. 7 schematically shows a method for determining at least one container corresponding to a target service according to target gateway cluster information, target gateway information, and target service information according to an embodiment of the present disclosure. Example diagram of the operating status of each group.

As shown in Fig. 7, in 700, for each container group address information 701 in at least one container group address information, a detection network connection 702 with the container group may be established according to the container group address information 701. After the detection network connection 702 is established, operation S710 may be performed.

In operation S710, is a heartbeat detection packet sent by the container group received within a predetermined period of time?

If so, it can be determined that the running state of the container group belongs to the normal running state 703.

If not, it can be determined that the running state of the container group is in an abnormal running state 704.

According to an embodiment of the present disclosure, operation S240 may include the following operations.

Determine the target container group address information corresponding to the target container group. Establish an actual network connection with the target container group according to the target container group address information. Send the pending service request to the target container group based on the actual network connection.

According to an embodiment of the present disclosure, an actual network connection with the target container group can be established based on the target container group address information. The actual network connection can be used to characterize a long connection between the gatewayContrller and the target container group. A long connection can refer to a connection on which multiple data packets can be continuously sent. After the actual network connection is established, the to-be-processed gateway service request can be sent to the target container group through the actual network connection based on the application layer protocol.

According to an embodiment of the present disclosure, the application layer protocol may include at least one of the following: a full-duplex communication protocol based on the transmission control protocol (WebSocket), a hypertext transfer protocol (HTTP), and a message queuing telemetry transport protocol (MQTT).

FIG8 schematically shows an example diagram of a method for processing a gateway service request according to an embodiment of the present disclosure.

As shown in FIG. 8 , operations S801 to S814 schematically illustrate a method for processing a gateway service request.

In operation S801, k8s operation and maintenance can create a gateway cluster.

In operation S802, the k8s operation and maintenance can point the gateway cluster identifier to the system component.

In operation S803, k8s operation and maintenance can authorize the gateway cluster to business operation and maintenance.

In operation S804, the business operation and maintenance may create a gateway.

In operation S805, the business operation and maintenance can point the gateway identifier to the gateway cluster of k8s operation and maintenance.

In operation S806, the gateway cluster operated and maintained by k8s can allocate gateway address information to the gateway.

In operation S807, k8s operation and maintenance can send gateway address information to business operation and maintenance.

In operation S808, the service operation and maintenance may receive gateway address information.

In operation S809, the business operation and maintenance may authorize the gateway to the business user.

In operation S810 , a business user may create a service.

In operation S811 , the service user may point the service identifier to the gateway.

In operation S812, the service operation and maintenance gateway may allocate service port information for the service.

In operation S813, the service operation and maintenance may send the service port information to the service user.

In operation S814, the service user may receive service port information.

The above are only exemplary embodiments, but are not limited thereto, and may also include other gateway service request processing methods known in the art, as long as they can improve the stability of request processing and ensure high availability of resources and services.

FIG9 schematically shows a flow chart of a method for managing a cloud-native gateway system according to an embodiment of the present disclosure.

As shown in FIG. 9 , the management method 900 of the cloud native gateway system includes operations S910 to S920 .

In operation S910, a target gateway service request is processed using a gateway service request processing method to obtain a processing result, wherein the target gateway service request includes target gateway service configuration information, and the target gateway service configuration information is associated with a cloud native gateway system.

In operation S920, the cloud native gateway system is managed according to the processing result.

FIG10 schematically shows a block diagram of a device for processing a gateway service request according to an embodiment of the present disclosure.

As shown in FIG. 10 , the service request processing device 1000 may include a first determination module 1010 , a second determination module 1020 , a third determination module 1030 and a sending module 1040 .

The first determination module 1010 is used to determine, in response to receiving a pending service request, the target gateway cluster information corresponding to the target gateway cluster, the target gateway information corresponding to the target gateway, and the target service information corresponding to the target service according to a preset mapping relationship and the pending service configuration information in the pending service request.

The second determination module 1020 is used to determine the respective running status of at least one container group corresponding to the target service according to the target gateway cluster information, the target gateway information and the target service information.

The third determining module 1030 is configured to determine a target container group in the at least one container group according to the respective running states of the at least one container group corresponding to the target service.

The sending module 1040 is used to send the pending service request to the target container group, so that the target container group can process the pending service request.

According to an embodiment of the present disclosure, the first determination module 1010 may include a first determination submodule, a second determination submodule, a third determination submodule, a fourth determination submodule, and a fifth determination submodule.

The first determination submodule is used to determine target virtual Internet Protocol address information according to the service configuration information to be processed.

The second determining submodule is used to determine the target gateway cluster information corresponding to the target gateway cluster according to the first preset mapping relationship and the target virtual Internet Protocol address information.

The third determination submodule is used to determine the gateway address information corresponding to the target gateway and the service port information corresponding to the target service according to the target gateway cluster information.

The fourth determining submodule is used to determine the target gateway information according to the second preset mapping relationship and the gateway address information.

The fifth determining submodule is used to determine the target service information according to the third preset mapping relationship and the service port information.

According to an embodiment of the present disclosure, the target gateway cluster includes at least one gateway, each of the at least one gateway corresponds to at least one service, the at least one gateway corresponds to gateway address information, and the at least one service corresponds to service port information.

According to an embodiment of the present disclosure, the third determining submodule may include a first determining unit, a second determining unit, and a third determining unit.

The first determining unit is used to determine the network segment range of the target gateway cluster according to the target gateway cluster information.

The second determining unit is configured to determine, for each gateway of the at least one gateway, gateway address information corresponding to the gateway according to a network segment range of the target gateway cluster.

The third determining unit is configured to determine, for each service of at least one service corresponding to the gateway, service port information of the service corresponding to the gateway according to the gateway address information corresponding to the gateway.

According to an embodiment of the present disclosure, the first determining submodule may include a processing unit and a fourth determining unit.

The processing unit is used to parse the service configuration information to be processed in response to receiving the service request to be processed, and obtain the domain name information corresponding to the service request to be processed.

The fourth determining unit is used to determine the target virtual network address information according to the domain name information.

According to an embodiment of the present disclosure, the second preset mapping relationship includes at least one second key-value relationship, the second key-value relationship includes second key information and second value information, and the at least one second key-value relationship can be constructed in the following manner.

For each second key-value relationship in at least one second key-value relationship, in response to receiving a gateway creation instruction, a gateway identifier, gateway configuration information, and a gateway cluster identifier are obtained. According to the gateway cluster identifier, virtual network address information corresponding to the gateway cluster identifier is determined. According to the target routing protocol and the virtual network address information, the gateway address information corresponding to the gateway identifier is determined. The gateway address information is determined as the second key information. The gateway configuration information is determined as the second value information. A second key-value relationship is constructed according to the second key information and the second value information.

According to an embodiment of the present disclosure, when the target routing protocol is a border gateway protocol, determining the gateway address information corresponding to the gateway identifier according to the target routing protocol and the virtual network address information may include:

According to the virtual Internet Protocol address information, a first resource pool is configured, wherein the first resource pool includes at least one first candidate address information. According to the first resource pool, target address information is determined in the at least one first candidate address information. According to the border gateway protocol, the target address information is published via any two front-end proxies so as to determine the target address information as the gateway address information.

According to an embodiment of the present disclosure, when the target routing protocol is an equal-cost multi-path routing protocol, determining the gateway address information corresponding to the gateway identifier according to the target routing protocol and the virtual network address information may include:

According to the virtual Internet Protocol address information, a second resource pool is configured, wherein the second resource The source pool includes at least one second candidate address information. According to the second resource pool, the target address information is determined in the at least one second candidate address information. According to the equal-cost multi-path routing protocol, the equal-cost routing information corresponding to the target address information is configured. The equal-cost routing information is determined as the gateway address information.

According to an embodiment of the present disclosure, the third preset mapping relationship includes at least one third key-value relationship, the third key-value relationship includes third key information and third value information, and the at least one third key-value relationship can be constructed in the following manner.

For each third key-value relationship in at least one third key-value relationship, in response to receiving a service creation instruction, obtain a service identifier, service configuration information, and a gateway identifier. According to the gateway identifier, determine the gateway address information corresponding to the gateway identifier. According to the gateway address information, determine the service port information corresponding to the service identifier. Determine the service port information as the third key information. Determine the service configuration information as the third value information. Construct a third key-value relationship according to the third key information and the third value information.

According to an embodiment of the present disclosure, the target service information includes container group address information corresponding to at least one container group.

According to an embodiment of the present disclosure, the second determining module 1020 may include a first establishing submodule, a sixth determining submodule and a seventh determining submodule.

The first establishing submodule is used to establish a detection network connection with the container group according to the container group address information for each container group address information in the at least one container group address information.

The sixth determining submodule is configured to determine that the running state of the container group is a normal running state when a heartbeat detection packet sent by the container group is received within a predetermined period of time.

The seventh determining submodule is configured to determine that the running state of the container group is in an abnormal running state when no heartbeat detection packet sent by the container group is received within a predetermined period of time.

According to an embodiment of the present disclosure, the third determining module 1030 may include an eighth determining submodule.

The eighth determining submodule is configured to determine the container group as a target container group in response to the running state of the container group being in a normal running state.

According to an embodiment of the present disclosure, the sending module 1040 may include a ninth determining submodule, The second is to establish a submodule and a sending submodule.

The ninth determining submodule is configured to determine target container group address information corresponding to the target container group.

The second establishing submodule is used to establish an actual network connection with the target container group according to the address information of the target container group.

The sending submodule is used to send the pending service request to the target container group based on the actual network connection.

FIG11 schematically shows a block diagram of a device for processing a gateway service request according to an embodiment of the present disclosure.

As shown in FIG. 11 , the management device 1100 of the cloud-native gateway system may include a processing module 1110 and a management module 1120 .

The processing module 1110 is used to utilize the processing device of the gateway service request to process the target gateway service request and obtain the processing result, wherein the target gateway service request includes the target gateway service configuration information, and the target gateway service configuration information is associated with the cloud native gateway system.

The management module 1120 is used to manage the cloud native gateway system according to the processing results.

According to the embodiments of the present invention, any one or more of the modules, submodules, units, and subunits, or at least part of the functions of any one of them can be implemented in one module. According to the embodiments of the present invention, any one or more of the modules, submodules, units, and subunits can be split into multiple modules for implementation. According to the embodiments of the present invention, any one or more of the modules, submodules, units, and subunits can be at least partially implemented as hardware circuits, such as field programmable gate arrays (FPGAs), programmable logic arrays (PLAs), systems on chips, systems on substrates, systems on packages, application specific integrated circuits (ASICs), or can be implemented by hardware or firmware in any other reasonable way of integrating or packaging the circuit, or implemented in any one of the three implementation methods of software, hardware, and firmware, or in any appropriate combination of any of them. Alternatively, according to the embodiments of the present invention, one or more of the modules, submodules, units, and subunits can be at least partially implemented as computer program modules, and when the computer program modules are run, the corresponding functions can be performed.

For example, any multiple of the first determination module 1010, the second determination module 1020, the third determination module 1030 and the sending module 1040 may be combined into one module/unit/sub-unit for implementation. Or any one of the modules/units/subunits can be split into multiple modules/units/subunits. Or, at least part of the functions of one or more modules/units/subunits in these modules/units/subunits can be combined with at least part of the functions of other modules/units/subunits and implemented in one module/unit/subunit. According to an embodiment of the present disclosure, at least one of the first determination module 1010, the second determination module 1020, the third determination module 1030 and the sending module 1040 can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application specific integrated circuit (ASIC), or can be implemented by hardware or firmware such as any other reasonable way of integrating or packaging the circuit, or by any one of the three implementation methods of software, hardware and firmware or by a suitable combination of any of them. Alternatively, at least one of the first determination module 1010 , the second determination module 1020 , the third determination module 1030 and the sending module 1040 may be at least partially implemented as a computer program module, and when the computer program module is executed, a corresponding function may be performed.

It should be noted that the processing device part of the gateway service request in the embodiment of the present disclosure corresponds to the processing method part of the gateway service request in the embodiment of the present disclosure. The description of the processing device part of the gateway service request specifically refers to the processing method part of the gateway service request, which will not be repeated here.

For example, any multiple of the processing modules 1110 and the management modules 1120 may be combined in one module/unit/sub-unit for implementation, or any one of the modules/units/sub-units may be split into multiple modules/units/sub-units. Alternatively, at least part of the functions of one or more of these modules/units/sub-units may be combined with at least part of the functions of other modules/units/sub-units and implemented in one module/unit/sub-unit. According to an embodiment of the present disclosure, at least one of the processing modules 1110 and the management modules 1120 may be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application specific integrated circuit (ASIC), or may be implemented by hardware or firmware such as any other reasonable way of integrating or packaging the circuit, or may be implemented in any one of the three implementation methods of software, hardware, and firmware, or in an appropriate combination of any of them. Alternatively, at least one of the processing modules 1110 and the management modules 1120 may be at least partially implemented as a computer program module, When the computer program module is executed, the corresponding function can be executed.

It should be noted that the management device part of the cloud native gateway system in the embodiment of the present disclosure corresponds to the management method part of the cloud native gateway system in the embodiment of the present disclosure. The description of the management device part of the cloud native gateway system specifically refers to the management method part of the cloud native gateway system, which will not be repeated here.

Figure 12 schematically shows a block diagram of an electronic device suitable for implementing a method for processing a gateway service request and a method for managing a cloud native gateway system according to an embodiment of the present disclosure. The electronic device shown in Figure 12 is only an example and should not impose any limitations on the functions and scope of use of the embodiment of the present disclosure.

As shown in FIG12 , a computer electronic device 1200 according to an embodiment of the present disclosure includes a processor 1201, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1202 or a program loaded from a storage portion 1209 into a random access memory (RAM) 1203. The processor 1201 may, for example, include a general-purpose microprocessor (e.g., a CPU), an instruction set processor and/or a related chipset and/or a dedicated microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 1201 may also include an onboard memory for caching purposes. The processor 1201 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

In RAM 1203, various programs and data required for the operation of electronic device 1200 are stored. Processor 1201, ROM 1202 and RAM 1203 are connected to each other through bus 1204. Processor 1201 performs various operations of the method flow according to the embodiment of the present disclosure by executing the program in ROM 1202 and/or RAM 1203. It should be noted that the program can also be stored in one or more memories other than ROM 1202 and RAM 1203. Processor 1201 can also perform various operations of the method flow according to the embodiment of the present disclosure by executing the program stored in the one or more memories.

According to an embodiment of the present disclosure, the electronic device 1200 may further include an input/output (I/O) interface 1205, which is also connected to the bus 1204. The electronic device 1200 may further include one or more of the following components connected to the I/O interface 1205: an input portion 1206 including a keyboard, a mouse, etc.; an output portion 1207 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage portion 1208 including a hard disk, etc. The storage unit 1208 includes a communication unit 1209 including a network interface card such as a LAN card, a modem, etc. The communication unit 1209 performs communication processing via a network such as the Internet. A drive 1210 is also connected to the I/O interface 1205 as needed. A removable medium 1211, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 1210 as needed, so that a computer program read therefrom is installed into the storage unit 1208 as needed.

According to an embodiment of the present disclosure, the method flow according to an embodiment of the present disclosure can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program carried on a computer-readable storage medium, and the computer program contains a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 1209, and/or installed from the removable medium 1211. When the computer program is executed by the processor 1201, the above-mentioned functions defined in the system of the embodiment of the present disclosure are executed. According to an embodiment of the present disclosure, the system, equipment, device, module, unit, etc. described above can be implemented by a computer program module.

The present disclosure also provides a computer-readable storage medium, which may be included in the device/apparatus/system described in the above embodiments; or may exist independently without being assembled into the device/apparatus/system. The above computer-readable storage medium carries one or more programs, and when the above one or more programs are executed, the method according to the embodiment of the present disclosure is implemented.

According to an embodiment of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium. For example, it may include, but is not limited to: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that may be used by or in combination with an instruction execution system, apparatus, or device.

For example, according to an embodiment of the present disclosure, the computer-readable storage medium may include the ROM 1202 and/or RAM 1203 described above and/or one or more memories other than ROM 1202 and RAM 1203.

Embodiments of the present disclosure also include a computer program product, which includes a computer program, The computer program includes program code for executing the method provided by the embodiment of the present disclosure. When the computer program product is running on an electronic device, the program code is used to enable the electronic device to implement the method for processing gateway service requests and the method for managing a cloud-native gateway system provided by the embodiment of the present disclosure.

When the computer program is executed by the processor 1201, the above functions defined in the system/device of the embodiment of the present disclosure are executed. According to the embodiment of the present disclosure, the system, device, module, unit, etc. described above can be implemented by a computer program module.

In one embodiment, the computer program may rely on tangible storage media such as optical storage devices, magnetic storage devices, etc. In another embodiment, the computer program may also be transmitted and distributed in the form of signals on a network medium, and downloaded and installed through the communication part 1209, and/or installed from the removable medium 1211. The program code contained in the computer program may be transmitted using any appropriate network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

According to an embodiment of the present disclosure, the program code for executing the computer program provided by the embodiment of the present disclosure can be written in any combination of one or more programming languages. Specifically, these computing programs can be implemented using high-level process and/or object-oriented programming languages, and/or assembly/machine languages. Programming languages include, but are not limited to, Java, C++, python, "C" language or similar programming languages. The program code can be executed entirely on the user computing device, partially on the user device, partially on the remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device can be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computing device (for example, using an Internet service provider to connect through the Internet).

The flowcharts and block diagrams in the accompanying drawings illustrate the possible architectures, functions, and operations of the systems, methods, and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flowchart or block diagram may represent a module, a program segment, or a portion of code, which contains one or more executable instructions for implementing the specified logical functions. It should also be noted that in some alternative implementations, the functions marked in the boxes may also occur in an order different from that marked in the accompanying drawings. For example, two The boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flow chart, and the combination of boxes in the block diagram or flow chart, can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions. It will be understood by those skilled in the art that the features recorded in the various embodiments and/or claims of the present disclosure can be combined and/or combined in various ways, even if such combinations or combinations are not explicitly recorded in the present disclosure. In particular, without departing from the spirit and teachings of the present disclosure, the features recorded in the various embodiments and/or claims of the present disclosure can be combined and/or combined in various ways. All of these combinations and/or combinations fall within the scope of the present disclosure.

The embodiments of the present disclosure are described above. However, these embodiments are only for illustrative purposes and are not intended to limit the scope of the present disclosure. Although the embodiments are described above separately, this does not mean that the measures in the various embodiments cannot be used in combination to advantage. The scope of the present disclosure is defined by the attached claims and their equivalents. Without departing from the scope of the present disclosure, those skilled in the art may make a variety of substitutions and modifications, which should all fall within the scope of the present disclosure.

Claims (17)

A method for processing a gateway service request, comprising: In response to receiving a pending gateway service request, determining target gateway cluster information corresponding to the target gateway cluster, target gateway information corresponding to the target gateway, and target service information corresponding to the target service according to a preset mapping relationship and the pending gateway service configuration information in the pending gateway service request; Determine, according to the target gateway cluster information, the target gateway information, and the target service information, a respective running state of at least one container group corresponding to the target service; Determining a target container group in the at least one container group corresponding to the target service according to the respective running states of the at least one container group; and The to-be-processed gateway service request is sent to the target container group, so that the target container group processes the to-be-processed gateway service request. The method according to claim 1, wherein, in response to receiving a pending gateway service request, determining, according to a preset mapping relationship and the pending gateway service configuration information in the pending gateway service request, target gateway cluster information corresponding to the target gateway cluster, target gateway information corresponding to the target gateway, and target service information corresponding to the target service comprises: Determining target virtual Internet Protocol address information according to the to-be-processed gateway service configuration information; Determine the target gateway cluster information corresponding to the target gateway cluster according to the first preset mapping relationship and the target virtual Internet Protocol address information; Determine, according to the target gateway cluster information, the gateway address information corresponding to the target gateway and the service port information corresponding to the target service; Determining the target gateway information according to the second preset mapping relationship and the gateway address information; and The target service information is determined according to a third preset mapping relationship and the service port information. The method according to claim 2, wherein the target gateway cluster includes at least one gateway, each of the at least one gateway corresponds to at least one server The at least one gateway has gateway address information corresponding to each of the at least one services, and the at least one service has service port information corresponding to each of the at least one services; The determining, according to the target gateway cluster information, the gateway address information corresponding to the target gateway and the service port information corresponding to the target service comprises: Determine the network segment range of the target gateway cluster according to the target gateway cluster information; For each gateway of the at least one gateway, Determining the gateway address information corresponding to the gateway according to the network segment range of the target gateway cluster; and For each of the at least one service corresponding to the gateway, The service port information of the service corresponding to the gateway is determined according to the gateway address information corresponding to the gateway. The method according to claim 2, wherein, in response to receiving the pending gateway service request, determining the target virtual Internet Protocol address information according to the pending gateway service configuration information comprises: In response to receiving the pending gateway service request, parsing the pending gateway service configuration information to obtain domain name information corresponding to the pending gateway service request; and The target virtual network address information is determined according to the domain name information. The method according to claim 2, wherein the second preset mapping relationship includes at least one second key-value relationship, the second key-value relationship includes second key information and second value information, and the at least one second key-value relationship is constructed in the following manner: For each second key-value relationship in the at least one second key-value relationship, In response to receiving the gateway creation instruction, obtaining a gateway identifier, gateway configuration information, and a gateway cluster identifier; According to the gateway cluster identifier, determining virtual network address information corresponding to the gateway cluster identifier; Determine the gateway address information corresponding to the gateway identifier according to the target routing protocol and the virtual network address information; Determining the gateway address information as the second key information; determining the gateway configuration information as the second value information; and The second key-value relationship is constructed according to the second key information and the second value information. The method according to claim 5, wherein, when the target routing protocol is a border gateway protocol, The determining, according to the target routing protocol and the virtual network address information, the gateway address information corresponding to the gateway identifier comprises: According to the virtual Internet Protocol address information, configuring a first resource pool, wherein the first resource pool includes at least one first candidate address information; determining target address information from the at least one first candidate address information according to the first resource pool; and According to the border gateway protocol, the target address information is published via any two front-end proxies, so as to determine the target address information as the gateway address information. The method according to claim 5, wherein, when the target routing protocol is an equal-cost multi-path routing protocol, The determining, according to the target routing protocol and the virtual network address information, the gateway address information corresponding to the gateway identifier comprises: According to the virtual Internet Protocol address information, configuring a second resource pool, wherein the second resource pool includes at least one second candidate address information; determining target address information in the at least one second candidate address information according to the second resource pool; According to the equal-cost multi-path routing protocol, configuring equal-cost routing information corresponding to the target address information; and The equal-cost routing information is determined as the gateway address information. The method according to claim 2, wherein the third preset mapping relationship includes at least one third key-value relationship, the third key-value relationship includes third key information and third value information, and the at least one third key-value relationship is constructed in the following manner: For each third key-value relationship in the at least one third key-value relationship, In response to receiving the service creation instruction, obtaining a service identifier, service configuration information, and a gateway identifier; According to the gateway identifier, determining the gateway address information corresponding to the gateway identifier; Determine the service port information corresponding to the service identifier according to the gateway address information; Determining the service port information as the third key information; determining the service configuration information as the third value information; and The third key-value relationship is constructed according to the third key information and the third value information. The method according to any one of claims 1 to 8, wherein the target service information includes container group address information corresponding to each of the at least one container groups; The determining, according to the target gateway cluster information, the target gateway information, and the target service information, the respective running states of at least one container group corresponding to the target service comprises: For each container group address information in the at least one container group address information, Establishing a detection network connection with the container group according to the container group address information; In the case where a heartbeat detection packet sent by the container group is received within a predetermined period of time, determining that the running state of the container group is a normal running state; and When no heartbeat detection packet sent by the container group is received within the predetermined period of time, it is determined that the running state of the container group is in an abnormal running state. The method according to claim 9, wherein determining the target container group in the at least one container group corresponding to the target service according to the respective running states of the at least one container group comprises: In response to the running state of the container group being a normal running state, the container group is determined as the target container group. The method according to any one of claims 1 to 8, wherein sending the pending gateway service request to the target container group comprises: Determine target container group address information corresponding to the target container group; Establishing an actual network connection with the target container group according to the target container group address information; and Based on the actual network connection, the pending gateway service request is sent to the The target container group. A method for managing a cloud native gateway system, comprising: Using the method described in any one of claims 1 to 11, processing a target gateway service request to obtain a processing result, wherein the target gateway service request includes target gateway service configuration information, and the target gateway service configuration information is associated with a cloud native gateway system; and The cloud native gateway system is managed according to the processing result. A device for processing a gateway service request, comprising: A first determination module is used to determine, in response to receiving a pending gateway service request, target gateway cluster information corresponding to the target gateway cluster, target gateway information corresponding to the target gateway, and target service information corresponding to the target service according to a preset mapping relationship and the pending gateway service configuration information in the pending gateway service request; A second determination module is used to determine the respective running status of at least one container group corresponding to the target service according to the target gateway cluster information, the target gateway information and the target service information; A third determining module, configured to determine a target container group from the at least one container group corresponding to the target service according to a respective running state of the at least one container group; and The sending module is used to send the to-be-processed gateway service request to the target container group, so that the target container group processes the to-be-processed gateway service request. A management device for a cloud native gateway system, comprising: A processing module, configured to process a target gateway service request using the apparatus of claim 13 to obtain a processing result, wherein the target gateway service request includes target gateway service configuration information, and the target gateway service configuration information is associated with a cloud native gateway system; and A management module is used to manage the cloud native gateway system according to the processing result. An electronic device, comprising: one or more processors; a memory for storing one or more instructions, Wherein, when the one or more instructions are executed by the one or more processors, The one or more processors are caused to implement the method of any one of claims 1 to 11 or claim 12. A computer-readable storage medium having executable instructions stored thereon, wherein when the executable instructions are executed by a processor, the processor implements the method of any one of claims 1 to 11 or claim 12. A computer program product, comprising computer executable instructions, wherein the computer executable instructions are used to implement the method of any one of claims 1 to 11 or claim 12 when executed.