CN116389599A

CN116389599A - Gateway service request processing method and device and cloud native gateway system management method and device

Info

Publication number: CN116389599A
Application number: CN202310288631.7A
Authority: CN
Inventors: 韩相元; 刘凯; 赵建星
Original assignee: Jingdong Technology Information Technology Co Ltd
Current assignee: Jingdong Technology Information Technology Co Ltd
Priority date: 2023-03-22
Filing date: 2023-03-22
Publication date: 2023-07-04

Abstract

The disclosure provides a gateway service request processing method, a cloud native gateway system management method and a cloud native gateway system management device, which can be applied to the fields of network technology and cloud native technology. The gateway service request processing method comprises the following steps: in response to receiving the gateway service request to be processed, determining target gateway cluster information corresponding to the target gateway, target gateway information corresponding to the target gateway and target service information corresponding to the target service according to a preset mapping relation and the gateway service configuration information to be processed in the gateway service request to be processed; determining respective running states 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 in the at least one container group according to respective operation states of the at least one container group corresponding to the target service; and sending the gateway service request to be processed to the target container group so that the target container group can process the gateway service request to be processed.

Description

Gateway service request processing method and device and cloud native gateway system management method and device

Technical Field

The present disclosure relates to the field of network technology and the field of cloud native technology, and more particularly, to a service request processing method, a cloud native gateway system management method and apparatus, an electronic device, a computer readable storage medium, and a computer program product.

Background

An API (Application Programming Interface ) gateway may refer to a unified portal on the system boundary that provides external access to internal interface services. Kubernetes may include a set of API resources under different gateway definitions.

For example, an Ingress API resource set under the definition of an Ingress Gateway and a Gateway API resource set under the definition of a Gateway. An Ingress API resource set and a Gateway API resource set.

In the process of implementing the disclosed concept, the inventor finds that at least the following problems exist in the related art: high availability of resources and services in Kubernetes cannot be guaranteed.

Disclosure of Invention

In view of this, the present disclosure provides a method for processing a service request, a method and apparatus 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, there is provided a method for processing a gateway service request, including:

In response to receiving a gateway service request to be processed, determining target gateway cluster information corresponding to a target gateway, target gateway information corresponding to the target gateway and target service information corresponding to target service according to a preset mapping relation and the gateway service configuration information to be processed in the gateway service request to be processed;

determining respective operation states 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 in the at least one container group according to the respective operation states of the at least one container group corresponding to the target service; and

and sending the gateway service request to be processed to the target container group so that the target container group can process the gateway service request to be processed.

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

Determining target virtual Internet protocol address information according to the gateway service configuration information to be processed;

determining target gateway cluster information corresponding to the target gateway cluster according to a first preset mapping relation and the target virtual internet protocol address information;

determining gateway address information corresponding to the target gateway and service port information corresponding to the target service according to the target gateway cluster information;

determining the target gateway information according to a second preset mapping relation and the gateway address information; and

and determining the target service information according to a third preset mapping relation 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, according to the target gateway cluster information, gateway address information corresponding to the target gateway and service port information corresponding to the target service includes:

Determining the network segment range of the target gateway cluster according to the target gateway cluster information

Determining, for each gateway of the at least one gateway, 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 based on gateway address information corresponding to the gateway.

According to an embodiment of the present disclosure, the determining, in response to receiving the pending service request, target virtual internet protocol address information according to the pending gateway service configuration information includes:

responding to the received gateway service request to be processed, analyzing the gateway service configuration information to be processed to obtain domain name information corresponding to the gateway service request to be processed; and

and determining the target virtual network address information according to the domain name information.

According to an embodiment of the disclosure, the first preset mapping relationship includes at least one second key value relationship, where the second key value relationship includes second key information and second value information, and the at least one second key value relationship is constructed by:

For each second key relation in the at least one second key relation, responding to the received gateway creation instruction, and acquiring a gateway identifier, gateway configuration information and gateway cluster identifier;

determining virtual network address information corresponding to the gateway cluster identifier according to the gateway cluster identifier;

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

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

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

and constructing the second key value relation according to the second key information and the second value information.

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

configuring a first resource pool according to the virtual internet protocol address information, wherein the first resource pool comprises at least one first candidate address information;

determining target address information in 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 issued 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, in a case where the target routing protocol is an equal cost multi-path routing protocol, determining gateway address information corresponding to the gateway identifier according to the target routing protocol and the virtual network address information includes:

configuring a second resource pool according to the virtual internet protocol address information, wherein the second resource pool comprises 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 equivalent multipath routing protocol, configuring equivalent routing information corresponding to the target address information; and

and determining the equivalent route information as the gateway address information.

According to an embodiment of the 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 by:

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

determining gateway address information corresponding to the gateway identifier according to the gateway identifier;

determining 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

and constructing the third key value relationship based on 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 determining, according to the target gateway cluster information, the target gateway information, and the target service information, an operation state of each of at least one container group corresponding to the target service includes:

establishing a probe 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;

Under the condition that the heartbeat detection packet sent by the container group is received in a preset period, determining that the running state of the container group belongs to a normal running state; and

and under the condition that the heartbeat detection packet sent by the container group is not received within the preset time period, determining that the running state of the container group belongs to an abnormal running state.

According to an embodiment of the present disclosure, determining the target container group among the at least one container group according to the respective operation states of the at least one container group corresponding to the target service includes:

and determining the container group as the target container group in response to the operation state of the container group belonging to the normal operation state.

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

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

establishing actual network connection with the target container group according to the address information of the target container group; and

and sending the service request to be processed to the target container group based on the actual network connection.

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

Processing a target gateway service request by using a processing method of the gateway service request to obtain a processing result, wherein the target gateway service request comprises target gateway service configuration information, and the target gateway service configuration information is associated with a cloud native gateway system; and

and managing the cloud native gateway system according to the processing result.

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

the first determining module is used for determining target gateway cluster information corresponding to the target gateway, target gateway information corresponding to the target gateway and target service information corresponding to the target service according to a preset mapping relation and the to-be-processed gateway service configuration information in the to-be-processed gateway service request in response to receiving the to-be-processed gateway service request;

a second determining module, configured to determine respective operation states 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 according to respective operation states of the at least one container group corresponding to the target service; and

And the sending module is used for sending the gateway service request to be processed to the target container group so that the target container group can process the gateway service request to be processed.

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

the processing module is used for processing a target gateway service request by utilizing a processing device of the gateway service request to obtain a processing result, wherein the target gateway service request comprises target gateway service configuration information, and the target gateway service configuration information is associated with a cloud native gateway system; and

and the management module is used for managing the cloud native gateway system according to the processing result.

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,

wherein the one or more instructions, when executed by the one or more processors, cause the one or more processors to implement a method as described in the present disclosure.

According to another aspect of the present disclosure, there is provided a computer-readable storage medium having stored thereon executable instructions that, when executed by a processor, cause the processor to implement a method as described in the present disclosure.

According to another aspect of the present disclosure, there is provided a computer program product comprising computer executable instructions which, when executed, are adapted to carry out the method as described in the present disclosure.

According to the embodiments of the present disclosure, since the target container group is determined according to the respective operation states of at least one container group corresponding to the target service, and the operation states are 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 operation states are normal operations. On the basis, the gateway service request to be processed is sent to the target container group, so that the gateway service request is automatically routed, and the gateway service request to be processed is processed by the target container group, so that the automatic processing of the gateway service request is realized, the technical problem that the high availability of resources and services in Kubernetes cannot be guaranteed in the related art is at least partially overcome, the stability of request processing is improved, and the high availability of resources and services is guaranteed.

Drawings

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

Fig. 1 schematically illustrates a system architecture to which a processing method of a gateway service request, a management method of a cloud native gateway system, may be applied according to an embodiment of the present disclosure;

fig. 2 schematically illustrates a flow chart of a method of processing a gateway service request according to an embodiment of the disclosure;

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

FIG. 4 schematically illustrates an example schematic diagram of building a second key-value relationship according to an embodiment of the disclosure;

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

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

FIG. 6 schematically illustrates an example schematic diagram of constructing a third key value relationship in accordance with an embodiment of the present disclosure;

Fig. 7 schematically illustrates an example schematic diagram of determining respective operation 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;

fig. 8 schematically illustrates an example schematic diagram of a method of processing a gateway service request according to an embodiment of the disclosure;

fig. 9 schematically illustrates an example schematic diagram of a management method of a cloud native gateway system according to an embodiment of the present disclosure;

FIG. 10 schematically illustrates a block diagram of a processing device of a service request according to an embodiment of the disclosure;

fig. 11 schematically illustrates an example schematic diagram of a management device of a cloud native gateway system according to an embodiment of the present disclosure; and

fig. 12 schematically illustrates a block diagram of an electronic device adapted to implement a processing method of a gateway service request, a management method of a cloud native gateway system, according to an embodiment of the disclosure.

Detailed Description

Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that the description is only exemplary and is not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the present disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. In addition, in the following description, descriptions of well-known structures and techniques are omitted so as not to unnecessarily obscure the concepts of the present disclosure.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and/or the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.

All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It should be noted that the terms used herein should be construed to have meanings consistent with the context of the present specification and should not be construed in an idealized or overly formal manner.

Where expressions like at least one of "A, B and C, etc. are used, the expressions should generally be interpreted in accordance with the meaning as commonly understood by those skilled in the art (e.g.," a system having at least one of A, B and C "shall include, but not be limited to, a system having a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.). Where a formulation similar to at least one of "A, B or C, etc." is used, in general such a formulation should be interpreted in accordance with the ordinary understanding of one skilled in the art (e.g. "a system with at least one of A, B or C" would include but not be limited to systems with a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.).

In embodiments of the present disclosure, the collection, updating, analysis, processing, use, transmission, provision, disclosure, storage, etc., of the data involved (including, but not limited to, user personal information) all comply with relevant legal regulations, are used for legal purposes, and do not violate well-known. In particular, necessary measures are taken for personal information of the user, illegal access to personal information data of the user is prevented, and personal information security, network security and national security of the user are maintained.

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

For example, after collecting the gateway service configuration information to be processed, the user information may be desensitized in a manner including de-identification or anonymization to secure the user information.

The API gateway can receive the request of the client, forward the request to the corresponding back-end system service according to the preset strategy and route, and process the result returned by the back-end service.

Resources in the Ingress API resource set and the gateway API resource set can together build a model for various network use cases. The gateway API resource set may include at least one of: a gateway resource, an HTTPRoute resource, a TCPRoute resource, and a Service resource. The gateway API may enable decoupling of configuration by separating resource objects to facilitate management of resources by personnel of different roles.

However, since there are fewer attributes in the Ingress gateway definition, path paths, port ports, etc. for host domain names. For the functions of header rewriting, hosts rewriting, weighting and the like, additional addition is required to be performed through annotation in the definition of the Ingress gateway, so that the user experience is poor. In addition, since the current gateway definition only formulates a specification, the gateway controller actually assuming the routing rule delivery is not realized in the ground.

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

In order to at least partially solve the technical problems in the related art, the present disclosure provides a method for processing a gateway service request, and a method and apparatus for managing a cloud native gateway system, which can be applied to the network technical field and the cloud native technical field. The gateway service request processing method comprises the following steps: in response to receiving the gateway service request to be processed, determining target gateway cluster information corresponding to the target gateway, target gateway information corresponding to the target gateway and target service information corresponding to the target service according to a preset mapping relation and the gateway service configuration information to be processed in the gateway service request to be processed; determining respective running states 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 in the at least one container group according to respective operation states of the at least one container group corresponding to the target service; and sending the gateway service request to be processed to the target container group so that the target container group can process the gateway service request to be processed.

It should be noted that, the processing method of the gateway service request and the management method and device of the cloud native gateway system provided in the embodiments of the present disclosure may be used in the network technical field and the cloud native technical field, for example, in the container technical field. The processing method of the gateway service request, the management method and the device of the cloud native gateway system provided by the embodiment of the disclosure can also be used in any field except the network technical field and the cloud native technical field, for example, in the information processing technical field. The application fields of the gateway service request processing method, the cloud native gateway system management method and the device provided by the embodiment of the disclosure are not limited.

Fig. 1 schematically illustrates a system architecture to which a processing method of a gateway service request, and a management method of a cloud native gateway system may be applied according to an embodiment of the present disclosure. It should be noted that fig. 1 is only an example of a system architecture to which embodiments of the present disclosure may be applied to assist those skilled in the art in understanding the technical content of the present disclosure, but does not mean that embodiments of the present disclosure may not be used in other devices, systems, environments, or scenarios.

As shown in fig. 1, a 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 a medium used to provide 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 fiber optic cables, among others.

The user may interact with the server 105 through the network 104 using at least one of the first terminal device 101, the second terminal device 102, the third terminal device 103, to receive or send messages, etc. Various communication client applications, such as a shopping class application, a web browser application, a search class application, an instant messaging tool, a mailbox client, social platform software, etc. (by way of example only) may be installed on the first terminal device 101, the second terminal device 102, and the third terminal device 103.

The first terminal device 101, the second terminal device 102, the third terminal device 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smartphones, tablets, laptop and desktop computers, and the like.

The server 105 may be a server providing various services, such as a background management server (by way of example only) providing support for websites browsed by the user 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 the user request, and feed back the processing result (e.g., the web page, information, or data obtained or generated according to the user request) to the terminal device.

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

Alternatively, the processing method of the gateway service request and the management method of the cloud native gateway system provided by the embodiments of the present disclosure may also be performed by the first terminal device 101, the second terminal device 102, or the third terminal device 103, or may also be performed by other terminal devices different from the first terminal device 101, the second terminal device 102, or the third terminal device 103. Accordingly, the processing apparatus for gateway service request and the management apparatus for cloud native gateway system provided in the embodiments of the present disclosure may also be disposed in the first terminal device 101, the second terminal device 102 or the third terminal device 103, or disposed 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 fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

It should be noted that the sequence numbers of the respective operations in the following methods are merely representative of the operations for the purpose of description, and should not be construed as representing the order of execution of the respective operations. The method need not be performed in the exact order shown unless explicitly stated.

Fig. 2 schematically illustrates a flow chart of a method of processing a gateway service request according to an embodiment of the 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 the gateway service request to be processed, target gateway cluster information corresponding to the target gateway, target gateway information corresponding to the target gateway, and target service information corresponding to the target service are determined according to the preset mapping relationship and the gateway service configuration information to be processed in the gateway service request to be processed.

In operation S220, respective operation states of at least one container group corresponding to the target service are 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 among the at least one container group according to respective operation states of the at least one container group corresponding to the target service.

In operation S240, the pending gateway service request is transmitted to the target container group so that the target container group processes the pending gateway service request.

According to embodiments of the present disclosure, the method of processing gateway service requests may be implemented based on the container orchestration engine Kubernetes. In Kubernetes, multiple containers may be created, one application instance running in each container, and management and access to the application instance may be achieved through built-in policies. For example, services within Kubernetes may be exposed outside the cluster through gateway proxies or requests outside the cluster may be forwarded inside the cluster for access by clients outside the cluster.

In accordance with embodiments of the present disclosure, the manner in which interaction between Kubernetes and clients is achieved may include at least one of: approaches based on Ingress and Ingress Controller, approaches based on gateway and gateway controller. Ingress and gateway may refer to routing rules customized by clients. IngressController and gatewayController may be provided by software vendors and may dynamically perceive changes in routing rules in the cluster through interactions with the Kubernetes.

According to the embodiment of the disclosure, a code for generating a gateway service request to be processed may be written in a target script in advance, and in response to detecting a gateway service processing operation initiated by a target user by using a target terminal, the target terminal may run the target script, generate a gateway service request message to be processed, and send the message to a server, so that the server processes the gateway service request message to be processed.

According to an embodiment of the present disclosure, the preset mapping relationship may include at least one of: a preset mapping relationship between virtual internet protocol address (Virtual IP 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 embodiments of the present disclosure, gateway cluster information may be used to describe different gateway clusters. The gateway cluster information may include at least one of a gateway cluster identity and a gateway cluster name. For example, virtual internet protocol address information that matches the service configuration information to be processed may be determined according to a preset mapping relationship between the virtual internet protocol address information and the gateway cluster information, in which case the gateway cluster information corresponding to the virtual internet protocol address information may be determined as target gateway cluster information.

According to an embodiment of the present disclosure, a gateway cluster may include at least one gateway. The at least one gateway may each correspond to gateway address information. For example, a gateway may refer to an API gateway (i.e., application Programming Interface, application program interface gateway). The gateway may comprise at least one of: spring Cloud Gateway gateway and ng inx gateway. The gateway may route the request received from the client in order to forward the request to the corresponding backend service. In addition, the gateway may route data received from the backend service in order to forward the data to the corresponding client.

According to embodiments of the present disclosure, gateway information may be used to describe different gateways. The gateway information may include at least one of a gateway identification and a gateway name. For example, gateway address information that matches the service configuration information to be processed may be determined according to a preset mapping relationship between the gateway address information and the gateway information, in which case the gateway information corresponding to the gateway address information may be determined as target gateway information.

According to embodiments of the present disclosure, each of the at least one gateway may each correspond to at least one service. The at least one service may each 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 identification and a service name. For example, service port information that matches the service configuration information to be processed may be determined according to a preset mapping relationship between the service port information and the service information, in which case the service information corresponding to the service port information may be determined as target service information.

According to embodiments of the present disclosure, each of the at least one service may each correspond to at least one container group (i.e., pod). The container group may characterize the smallest deployable computing unit created and managed in the container cluster. Each of the at least one container group may include at least one container. The at least one container group may each correspond to container group address information. After the target gateway cluster information, the target gateway information, and the target service information are obtained, respective operation states of at least one container group may be determined according to respective container group address information of at least one container group corresponding to the target service. The operational status may be used to characterize whether the container group is operating properly.

According to an embodiment of the present disclosure, after obtaining the respective operation states of at least one container group corresponding to the target service, the target container group may be determined among the at least one container group according to the respective operation states of the at least one container group. For example, a set of containers whose operating state characterizes normal operation may be determined as the target set of containers.

According to the embodiment of the disclosure, after the target container group is determined, the gateway service request to be processed 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 gateway service request to be processed and returns a processing result message.

The method 200 for processing a gateway service request according to an embodiment of the present invention is further described below with reference to fig. 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 implemented based on gateway controller. The gateway controller can monitor gateway update events, assign virtual internet protocol addresses to the gateway, and store the gateway monitor content to a distributed registry service center (e.g., ETCD). In addition, gateway controller can monitor domain name, path, request parameter rewriting, back end and weight on httprote, and store httprote monitoring content to distributed registration service center.

According to the embodiment of the disclosure, the code logic of gateway controller is formed by expanding and supplementing the k8s-gateway standard on the basis of the v1beta version native semantics of gateway, thereby realizing gateway control plane service. The front-end proxy is utilized to dynamically add and delete the open-source gateway monitoring port, so that the data plane service is realized. On the basis, the scheduling of the VIP is completed through the coordination of gateway controller and front-end agent, so that the complete cloud native seven-layer gateway service is formed. This will be described below according to specific embodiments.

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

And determining target virtual Internet protocol address information according to the gateway service configuration information to be processed. And determining target gateway cluster information corresponding to the target gateway cluster according to the first preset mapping relation and the target virtual internet protocol address information. And determining gateway address information corresponding to the target gateway and service port information corresponding to the target service according to the target gateway cluster information. And determining target gateway information according to the second preset mapping relation and the gateway address information. And determining target service information according to the third preset mapping relation and the service port information.

According to embodiments of the present disclosure, gateway clusters, gateways, and services may belong to custom resources (Custom Resource Definition, CRD). After the gateway service configuration information to be processed is obtained, the gateway service configuration information to be processed can be processed to obtain a processing result. And determining the target virtual network address information according to the processing result. The target virtual network address information may be used to indicate a target gateway cluster. The processing manner of the service configuration information to be processed may be configured according to the actual service requirement, which is not limited herein. For example, the service configuration information to be processed may be parsed to obtain domain name information corresponding to the service request to be processed. On the 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 may be used to characterize a preset mapping relationship between virtual internet protocol address information and gateway cluster information. The first preset mapping relationship may include at least one first key value relationship. The first key-value relation may be created from the virtual internet protocol address information and the gateway cluster information. The first key-value relationship may include a one-to-one correspondence between virtual internet protocol address information and gateway cluster information. Gateway clusters may be characterized using gatewaycass. gatewaycass may refer to a group of gateways that have a common configuration and behavior. The gateway cluster can be used for describing the definition of k8s operation and maintenance on different gateway services, and realizing the gateway cluster which selectively authorizes the business operation and maintenance to meet the business scene.

According to an embodiment of the present disclosure, the second preset mapping relationship may be used to characterize a preset mapping relationship between gateway address information and gateway information. The gateway may use gateway characterization. gateway may refer to a point that is able to translate traffic to a service within a cluster. gateway can be used to describe the definition of the gateway usage scope by the service operation, e.g. what kind of service under the naspace can be used. In addition, gateway has VIP and monitoring port, and service operation can authorize service user conforming to use range through gateway.

According to an embodiment of the present disclosure, the third preset mapping relationship may be used to characterize a preset mapping relationship between service port information and service information. Routes may be characterized using httprote. httprote may refer to how traffic obtained through a gateway maps to a service. httprote may be used to describe matching rule descriptions of business users to business services, e.g., domain names, paths, and backend may be bound to gateway to implement externally exposed services.

According to the embodiment of the disclosure, since the target gateway cluster information is determined according to the first preset mapping relation and the target virtual internet protocol address information, the target gateway information is determined according to the second preset mapping relation and the gateway address information, and the target service information is determined according to the third preset mapping relation and the service port information, the target gateway cluster information, the target gateway information and the target service information are automatically determined according to the gateway service configuration information to be processed, the information processing efficiency is improved, and the processing efficiency of the gateway service request is further improved.

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

As shown in fig. 3, in 300, at least one gateway cluster includes gateway cluster 304_1 and gateway cluster 304_2, at least one gateway corresponding to gateway cluster 304_1 includes 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 is exemplarily shown as an information determining 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 may be determined from 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 relation, determining target gateway cluster information corresponding to the gateway cluster 304_2. The gateway address information 305 and the service port information 307 may be determined according to target gateway cluster information corresponding to the gateway cluster 304_2. The target gateway information corresponding to the gateway 304_21 may be determined according to the gateway address information 305 and the second preset mapping relation 306. The target service information corresponding to the service 304_212 may be determined according to the service port information 307 and the third preset mapping relation 308.

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

And responding to the received gateway service request to be processed, analyzing and processing the gateway service configuration information to be processed to obtain domain name information corresponding to the gateway service request to be processed. And determining target virtual network address information according to the domain name information.

According to embodiments of the present disclosure, domain name information may refer to the name of a computer or group of computers on the Internet that is made up of a string of names separated by dots. The domain name information may be used to identify the electronic orientation of the computer at the time of data transmission.

According to the embodiment of the disclosure, after obtaining the domain name information, domain name resolution processing may be further performed on the domain name information to map and convert the domain name information into an IP address, so as to obtain target virtual network address information. The domain name resolution processing manner may be configured according to actual service requirements, which is not limited herein. For example, the manner of domain name resolution processing may include at least one of: recursive parsing and iterative parsing. Recursive resolution may refer to completing the translation of names and addresses at once. Repeated resolution may refer to a single server per request.

According to an embodiment of the present disclosure, the at least one second key-value relation may be constructed as follows.

And for each second key relation in the at least one second key relation, responding to the received gateway creation instruction, and acquiring a gateway identifier, gateway configuration information and gateway cluster identifier. And determining virtual network address information corresponding to the gateway cluster identifier according to the gateway cluster identifier. And determining gateway address information corresponding to the gateway identification according to the target routing protocol and the virtual network address information. The gateway address information is determined as second key information. The gateway configuration information is determined as second value information. And constructing a second key value relation 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 relation may include second key information and second value information.

According to the embodiment of the disclosure, the Kubernetes cluster may acquire newly created gateway configuration information in case that the newly created gateway is monitored, and generate a gateway creation instruction according to the newly created gateway configuration information. The gateway configuration information may include at least one of: gateway identification and gateway cluster identification.

According to the embodiment of the disclosure, a code for generating a gateway creation instruction may be written in a first script in advance, and in response to detecting a gateway creation operation initiated by a target user using a target terminal, the target terminal may run the first script, generate a gateway creation instruction packet and send the packet to a server, so that the server creates a gateway according to the packet.

According to embodiments of the present disclosure, a target routing protocol may be used to enable translation between private network IP addresses and public network IP addresses to enable access to the internet. The private network IP address may refer to an address used in a local area network. The public network IP address may refer to an address directly accessible on the internet.

According to the embodiment of the disclosure, the target routing protocol may be configured according to actual service requirements, which is not limited herein. For example, the target routing protocol may include at least one of: ALL-IN mode routing protocol, equal cost multi-path routing protocol (Equal Cost Multi Path, ECMP), border gateway routing protocol (Border Gateway Protocol, BGP), and open shortest path first routing protocol (Open Shortest Path First, OSPF).

According to the embodiment of the disclosure, gateway address information corresponding to the gateway identification 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, a second key-value relationship may be created from the gateway address information and the gateway configuration information. 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: and determining at least one first similarity according to the gateway address information and the second key information corresponding to the at least one second key relation. And determining target second key information according to the at least one first similarity. And determining target second value information corresponding to the target second value information according to the target second key information. And determining target gateway information according to the gateway configuration information corresponding to the target second value information.

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

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

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

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

After the gateway address information 404 is obtained, the gateway address information 404 may be determined as second key information 405. The gateway configuration information 401_1 is determined as the second value information 406. A second key-value relation 407 is constructed from the second key information 405 and the second value information 406.

According to an embodiment of the present disclosure, in a case where the target routing protocol is a border gateway protocol, determining gateway address information corresponding to the gateway identification according to the target routing protocol and the virtual network address information may include the following operations.

And configuring a first resource pool according to the virtual internet protocol address information, wherein the first resource pool comprises at least one first candidate address information. And determining target address information in at least one first candidate address information according to the first resource pool. According to the border gateway protocol, destination address information is published via any two front-end agents in order to determine the destination address information as gateway address information.

According to embodiments of the present disclosure, border gateway protocol may refer to a dynamic routing protocol for exchanging routing information between different autonomous systems (Autonomous System, AS), or within the same autonomous system. For example, in the case where two autonomous systems need to exchange routing information, each autonomous system may be assigned a node running the border gateway protocol and the node may exchange routing information with other autonomous systems on behalf of the autonomous system.

According to embodiments of the present disclosure, a node running the border gateway protocol may include at least one of a host and a router. Taking a node as a router as an example, after the router receives the route information from an upstream neighbor, the router can lower and brush the optimal route in the dynamic routing protocol learned by the equipment to a driver to guide traffic forwarding, and can notify the neighbor of the optimal route in the dynamic routing protocol learned by the equipment.

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 VIP addresses. The at least one first candidate address information may be managed and scheduled by a gatewaycontroller. The first resource pool may comprise at least one of: a first Dynamic resource Pool (i.e., dynamic Pool) and a first Static resource Pool (i.e., static Pool).

According to the embodiment of the disclosure, after receiving the gateway creation instruction, a corresponding first resource pool may be configured for the terminal according to the virtual internet protocol address information. After the determined first resource pool, target address information may be determined from the at least one first candidate address information, and the target address information may be returned to the gateway. In addition, any two front-end agents (i.e., agents) may be notified of a task of issuing gateway address information corresponding to the gateway, and issue the target address information to the switch based on the border gateway protocol via the any two front-end agents and bind the target address information to the local loop back interface. The nodes of any two front-end agents can be set according to actual service requirements, and the nodes are not limited herein, and only an even number of nodes are required to be ensured. For example, there may be a 2n-th node and 2n+1-th node.

According to the embodiment of the disclosure, the front-end agent and the open source gateway (such as Apisix) can be deployed in the same container, multi-copy deployment is performed through the statefulset of k8s, the network mode adopts a host mode, and other containers can be repelled through the stain and the anti-affinity of k8s so as to realize the exclusive node. Multiple copy deployment may refer to implementing a election through k8s leases, i.e., only the master node is responsible for listening for events and reading and writing to the distributed registry. The front-end proxy can load the monitoring port read into the open source gateway, so that the front-end proxy can dynamically add and delete the monitoring port of the open source gateway.

According to embodiments of the present disclosure, gatewayController may coordinate with the front-end proxy to complete the scheduling of the VIP. For example, the PodIP and PodName may be mapped into the environment variables of the container through a downwardAPI of k8s, and the front end agent may intercept the sequence number from the PodName and report its own heartbeat and sequence number to the gatewayController. The gateway controller may perform bit operation on VIP to obtain a decimal sum of 4 segments of IP, and perform modulo remainder operation on the number of Apisix nodes to obtain corresponding nodes. The gateway controller may write the VIP into the distributed registry directory of the corresponding node to complete the VIP scheduling.

According to the embodiment of the disclosure, the target address information is determined in at least one first candidate address information according to the first resource pool, so that the automatic determination of the target address information is realized, the time for scheduling the VIP address is shortened, the processing efficiency of the VIP address scheduling is improved, and the efficiency for determining the gateway address information is further improved. On the basis, because the gateway address information is determined according to the border gateway protocol by issuing the target address information through any two front-end agents, the optimization of operation and business users is realized.

Fig. 5A schematically illustrates an example schematic diagram of determining gateway address information corresponding to a gateway identification 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 target address information 503 may be determined in the first candidate address information 502_1, the first candidate address information 502_2, …, the first candidate address information 502_p, …, 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 agent 505_1 and the front-end agent 505_2 in order to determine the target address information 503 as gateway address information 506.

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

And configuring a second resource pool according to the virtual internet protocol address information, wherein the second resource pool comprises at least one second candidate address information. And determining target address information in at least one second candidate address information according to the second resource pool. And configuring equivalent routing information corresponding to the target address information according to the equivalent multipath routing protocol. Equivalent routing information is determined as gateway address information.

According to embodiments of the present disclosure, an equal cost multipath routing protocol may refer to a network environment in which multiple links are used simultaneously in any network environment, i.e., there are multiple different links to reach the same destination address. The path selection method of the equal cost multipath routing protocol can be set according to the actual service requirement, and is not limited herein. For example, the path selection method may include at least one of: 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 VIP addresses. The at least one second candidate address information may be managed and scheduled by a gatewaycontroller. The second resource pool may comprise at least one of: a second Dynamic resource Pool (i.e., dynamic Pool) and a second Static resource Pool (i.e., static Pool).

According to embodiments of the present disclosure, VIP segments may be equivalently routed to all nodes of apisix by configuring equivalent routes on the switch. After receiving the gateway creation instruction, a corresponding second resource pool can be configured for the terminal according to the virtual internet protocol address information. After the determined second resource pool, destination address information may be determined from the at least one second candidate address information, equivalent routing information corresponding to the destination address information may be configured via an equivalent multipath routing protocol, and the equivalent routing information may be returned to the gateway.

According to the embodiment of the disclosure, when the target routing protocol is an ALL-IN mode routing protocol, apisix node IPs reported by the front-end proxy can be ALL returned to the gateway, and the service user selects 1 or more IP gateway address information therein. The implementation in this case is simpler.

According to the embodiment of the disclosure, the target address information is determined in at least one second candidate address information according to the second resource pool, so that the automatic determination of the target address information is realized, the time for scheduling the VIP address is shortened, the processing efficiency of the VIP address scheduling is improved, and the efficiency for determining the gateway address information is further improved. On the basis, because the gateway address information is determined by configuring the equivalent route information corresponding to the target address information according to the equivalent multipath route protocol, the gateway address information is friendly to service users, and the user experience is improved.

Fig. 5B schematically illustrates an example schematic diagram of determining gateway address information corresponding to a gateway identification 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 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 may be determined in 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 multipath routing protocol 510, the equal cost routing information 511 corresponding to the target address information 509 is configured. Equivalent routing information 511 is determined as gateway address information 512.

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

And determining the network segment range of the target gateway cluster according to the target gateway cluster information. And determining gateway address information corresponding to the gateways according to the network segment range of the target gateway cluster for each gateway in the at least one gateway. For each of at least one service corresponding to the gateway, service port information of the service corresponding to the gateway is determined according to 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 each correspond to at least one service. The at least one gateway may each correspond to gateway address information. The at least one service may each correspond to service port information.

According to the embodiment of the disclosure, after the target gateway cluster information is obtained, the network segment range of the target gateway cluster may be determined according to the target gateway cluster information. The segment range may be characterized using w.x.y.z. W, X, Y, Z E [0, 255]. For example, a segment range may be set with W e [0, 10], X e [0, 10], E [0, 10], Z e [0, 255], i.e., the segment range may include Internet protocol addresses in the range of 0.0.0.0-10.10.10.255. After obtaining the network segment range of the target gateway cluster, gateway address information corresponding to the gateway may be determined for each gateway of the at least one gateway, respectively.

According to an embodiment of the present disclosure, the at least one third key value relationship may be constructed as follows.

For each of the at least one third key value relationship, in response to receiving the service creation instruction, obtaining a service identification, service configuration information, and gateway identification. And determining gateway address information corresponding to the gateway identification according to the gateway identification. And determining service port information corresponding to the service identifier according to the gateway address information. Service port information is determined as third key information. The service configuration information is determined as third value information. And constructing a third key value relation 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 the embodiment of the disclosure, the Kubernetes cluster may acquire newly created service configuration information and generate a service creation instruction according to the newly created service configuration information when the newly created service is monitored. The service configuration information may include at least one of: container address, service domain name, service port, and service annotation information.

According to the embodiment of the disclosure, the code for generating the service creation instruction may be written in the second script in advance, and in response to detecting that the target user utilizes the service creation operation initiated by the target terminal, the target terminal may run the second script, generate a service creation instruction message and send the message to the server, so that the server creates the service according to the message.

According to the embodiment of the disclosure, gateway address information corresponding to the gateway identifier may be determined according to the gateway identifier. And determining service port information corresponding to the service identifier according to the gateway address information. After obtaining the service port information, a third key value relationship may be created from the service port information and the service configuration information. The third key-value relationship may include a one-to-one correspondence between service port information and 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 relation and the service port information may include: and determining at least one second similarity according to the service port information and the third key information corresponding to the at least one third key value relation. And determining target third key information according to the at least one second similarity. And determining target third value information corresponding to the target third value information according to the target third key information. And determining target service information according to the service configuration information corresponding to the target third value information.

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

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

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

Gateway address information 602 corresponding to gateway identification 601_2 may be determined from gateway identification 601_2. From the gateway address information 602, service port information 603 corresponding to the service identification 601_3 is determined.

Service port information 603 may be determined as third key information 604. The gateway service configuration information 601_1 is determined as the third value information 605. A third key value relationship 606 is constructed from the third key information 604 and the third value information 605.

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

For each container group address information of the at least one container group address information, a probe network connection with the container group is established according to the container group address information. And under the condition that the heartbeat detection packet sent by the container group is received in a preset period, determining that the running state of the container group belongs to a normal running state. And under the condition that the heartbeat detection packet sent by the container group is not received within a preset period, determining that the running state of the container group belongs to 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 group.

According to embodiments of the present disclosure, a probe network connection may be used to characterize a short connection between gatewayContrler and a container group. A short connection may refer to a connection being established only when data needs to be transmitted during data transmission, and the connection being disconnected after data transmission is completed, i.e. only one service is transmitted per connection. After the probe network connection is established, heartbeat probe packets may be sent to the container group based on the probe network connection.

According to an embodiment of the present disclosure, the heartbeat probe packet may refer to a custom command word that periodically informs each state of the other party between the gateway controller and the container group, and the heartbeat probe packet may be transmitted at predetermined time intervals. The predetermined period of time may be set according to actual service requirements, and is not limited herein. The predetermined period may be a detection time interval set in advance, for example, the predetermined 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 operational state of the container group belonging to the normal operational state, the container group is determined as the target container group.

According to an embodiment of the present disclosure, the abnormal operation state may be determined in a case where the heartbeat probe packet transmitted by the pod set is not received within a predetermined period of time. The normal operation state may be determined in a case where the heartbeat probe packet transmitted by the pod set 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 illustrates an example schematic diagram of determining respective operation 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.

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

Is a heartbeat probe packet sent by the pod group received within a predetermined period of time in operation S710?

If so, it may be determined that the operational status of the container group belongs to the normal operational status 703.

If not, it may be determined that the operational state of the group of containers belongs to the abnormal operational state 704.

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

Target container group address information corresponding to the target container group is determined. And establishing actual network connection with the target container group according to the address information of the target container group. Based on the actual network connection, the pending service request is sent to the target set of containers.

According to embodiments of the present disclosure, an actual network connection with a target container group may be established based on target container group address information. The actual network connection may be used to characterize a long connection between gatewaycorller and the target set of containers. A long connection may refer to a connection over which multiple data packets can be sent in succession. After the actual network connection is established, the pending gateway service request may be sent to the target set of containers over 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: full duplex communication protocol based on transmission control protocol (WebSocket), hypertext transfer protocol (HyperText Transfer Protocol, HTTP) and message queue telemetry transfer protocol (Message Queuing Telemetry Transport, MQTT).

Fig. 8 schematically illustrates an example schematic diagram of a method of processing a gateway service request according to an embodiment of the disclosure.

As shown in fig. 8, operations S801 to S814 schematically show a schematic diagram of a processing method of a gateway service request.

In operation S801, the k8S operation dimension may create a gateway cluster.

In operation S802, the k8S operation may point the gateway cluster identity to the present system component.

In operation S803, the k8S operation dimension may authorize the gateway cluster to the traffic operation dimension.

In operation S804, the service operation may create a gateway.

In operation S805, the traffic operation may point the gateway identification to the gateway cluster of the k8S operation.

The gateway cluster of the k8S operation may allocate gateway address information to the gateway in operation S806.

In operation S807, the k8S operation may transmit gateway address information to the service operation.

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

In operation S809, the service operation may authorize the gateway to the service user.

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

In operation S811, the service user may direct the service identity to the gateway.

The gateway of the traffic operation may allocate service port information for the service in operation S812.

In operation S813, the service operation may transmit service port information to the service user.

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

The foregoing is only an exemplary embodiment, but is not limited thereto, and other gateway service request processing methods known in the art may be also included, as long as the stability of request processing can be improved, and high availability of resources and services can be ensured.

Fig. 9 schematically illustrates a flowchart of a method of management of 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 by using a processing method of the gateway service request, and a processing result is obtained, where 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.

Fig. 10 schematically illustrates a block diagram of a processing apparatus of a gateway service request according to an embodiment of the disclosure.

As shown in fig. 10, the processing apparatus 1000 for a service request may include a first determination module 1010, a second determination module 1020, a third determination module 1030, and a transmission module 1040.

The first determining module 1010 is configured to determine, in response to receiving the service request to be processed, target gateway cluster information corresponding to the target gateway, target gateway information corresponding to the target gateway, and target service information corresponding to the target service according to a preset mapping relationship and service configuration information to be processed in the service request to be processed.

And a second determining module 1020, configured to determine respective operation states 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 among the at least one container group according to respective operation states of the at least one container group corresponding to the target service.

And the sending module 1040 is configured to send the service request to be processed to the target container group, so that the target container group processes the service request to be processed.

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

And the first determining submodule is used for determining target virtual internet protocol address information according to the service configuration information to be processed.

And the second determining submodule is used for determining target gateway cluster information corresponding to the target gateway cluster according to the first preset mapping relation and the target virtual internet protocol address information.

And the third determining submodule is used for determining gateway address information corresponding to the target gateway and service port information corresponding to the target service according to the target gateway cluster information.

And the fourth determining submodule is used for determining target gateway information according to the second preset mapping relation and the gateway address information.

And a fifth determining sub-module, configured to determine target service information according to the third preset mapping relationship and the service port information.

According to an embodiment of the present disclosure, the third determination sub-module may include a first determination unit, a second determination unit, and a third determination unit.

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

And the second determining unit is used for determining gateway address information corresponding to the gateways according to the network segment range of the target gateway cluster for each gateway in the at least one gateway.

And a third determining unit configured to determine, for each of at least one service corresponding to the gateway, service port information of the service corresponding to the gateway based on gateway address information corresponding to the gateway.

According to an embodiment of the present disclosure, the first determination sub-module may include a processing unit and a fourth determination unit.

And the processing unit is used for responding to the received service request to be processed, analyzing and processing the service configuration information to be processed and obtaining domain name information corresponding to the service request to be processed.

And the fourth determining unit is used for determining 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 may be constructed as follows.

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

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

According to an embodiment of the present disclosure, the third preset mapping relationship includes at least one third key value relationship including third key information and third value information, and the at least one third key value relationship may be constructed as follows.

According to an embodiment of the present disclosure, the second determination module 1020 may include a first establishment sub-module, a sixth determination sub-module, and a seventh determination sub-module.

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

And the sixth determining submodule is used for determining that the running state of the container group belongs to the normal running state when the heartbeat detection packet sent by the container group is received within a preset period.

And a seventh determining submodule, configured to determine that the operation state of the container group belongs to an abnormal operation state if the heartbeat detection packet sent by the container group is not received within a predetermined period.

According to an embodiment of the present disclosure, the third determination module 1030 may include an eighth determination sub-module.

And an eighth determining sub-module for determining the container group as the target container group in response to the operation state of the container group belonging to the normal operation state.

According to an embodiment of the present disclosure, the transmitting module 1040 may include a ninth determination sub-module, a second establishment sub-module, and a transmitting sub-module.

And a ninth determination submodule for determining target container group address information corresponding to the target container group.

And the second establishing submodule is used for establishing actual network connection with the target container group according to the address information of the target container group.

And the sending sub-module is used for sending the service request to be processed to the target container group based on the actual network connection.

Fig. 11 schematically illustrates a block diagram of a processing apparatus of a gateway service request according to an embodiment of the disclosure.

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

The processing module 1110 is configured to process, by using a processing device of the gateway service request, a target gateway service request to obtain a processing result, where 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 the management module 1120 is used for managing the cloud native gateway system according to the processing result.

Any number of modules, sub-modules, units, sub-units, or at least some of the functionality of any number of the sub-units according to embodiments of the present disclosure may be implemented in one module. Any one or more of the modules, sub-modules, units, sub-units according to embodiments of the present disclosure may be implemented as split into multiple modules. Any one or more of the modules, sub-modules, units, sub-units according to embodiments of the present disclosure may be implemented at least in part as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system-on-chip, a system-on-substrate, a system-on-package, an Application Specific Integrated Circuit (ASIC), or in any other reasonable manner of hardware or firmware that integrates or encapsulates the circuit, or in any one of or a suitable combination of three of software, hardware, and firmware. Alternatively, one or more of the modules, sub-modules, units, sub-units according to embodiments of the present disclosure may be at least partially implemented as computer program modules, which when executed, may perform the corresponding functions.

For example, any of the first determination module 1010, the second determination module 1020, the third determination module 1030, and the transmission module 1040 may be combined in one module/unit/sub-unit or any of them may be split into a plurality of modules/units/sub-units. Alternatively, at least some of the functionality of one or more of these modules/units/sub-units may be combined with at least some of the functionality of other modules/units/sub-units and implemented in one module/unit/sub-unit. According to embodiments 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 transmission module 1040 may be implemented at least in part as hardware circuitry, 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 in hardware or firmware in any other reasonable manner of integrating or packaging the circuits, or in any one of or a suitable combination of three of software, hardware, and firmware. Alternatively, at least one of the first determination module 1010, the second determination module 1020, the third determination module 1030, and the transmission module 1040 may be at least partially implemented as a computer program module, which when executed, may perform the corresponding functions.

It should be noted that, in the embodiment of the present disclosure, the processing device portion of the gateway service request corresponds to the processing method portion of the gateway service request in the embodiment of the present disclosure, and the description of the processing device portion of the gateway service request specifically refers to the processing method portion of the gateway service request, which is not described herein again.

For example, any number of the processing module 1110 and the management module 1120 may be combined in one module/unit/sub-unit or any one of them may be split into a plurality of modules/units/sub-units. Alternatively, at least some of the functionality of one or more of these modules/units/sub-units may be combined with at least some of the functionality of other modules/units/sub-units and implemented in one module/unit/sub-unit. According to embodiments of the present disclosure, at least one of the processing module 1110 and the management module 1120 may be implemented at least in part 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 in hardware or firmware, such as any other reasonable way of integrating or packaging the circuits, or in any one of or a suitable combination of three of software, hardware, and firmware. Alternatively, at least one of the processing module 1110 and the management module 1120 may be at least partially implemented as a computer program module, which when executed, may perform the corresponding functions.

It should be noted that, in the embodiment of the present disclosure, the management device portion of the cloud native gateway system corresponds to the management method portion of the cloud native gateway system in the embodiment of the present disclosure, and the description of the management device portion of the cloud native gateway system specifically refers to the management method portion of the cloud native gateway system, which is not described herein again.

Fig. 12 schematically illustrates a block diagram of an electronic device adapted to implement a processing method of a gateway service request, a management method of a cloud native gateway system, according to an embodiment of the disclosure. The electronic device shown in fig. 12 is merely an example and should not be construed to limit the functionality and scope of use of the disclosed embodiments.

As shown in fig. 12, 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 section 1209 into a Random Access Memory (RAM) 1203. The processor 1201 may include, for example, a general purpose microprocessor (e.g., a CPU), an instruction set processor and/or an associated chipset and/or special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), or the like. Processor 1201 may also include on-board memory for caching purposes. The processor 1201 may include a single processing unit or multiple processing units for performing the different actions of the method flows according to embodiments of the disclosure.

In the RAM 1203, various programs and data required for the operation of the electronic apparatus 1200 are stored. The processor 1201, the ROM 1202, and the RAM 1203 are connected to each other through a bus 1204. The processor 1201 performs various operations of the method flow according to the embodiments of the present disclosure by executing programs in the ROM 1202 and/or RAM 1203. Note that the program may be stored in one or more memories other than the ROM 1202 and the RAM 1203. The processor 1201 may also perform various operations of the method flow according to embodiments of the present disclosure by executing programs stored in the one or more memories.

According to an embodiment of the disclosure, the electronic device 1200 may also include an input/output (I/O) interface 1205, the input/output (I/O) interface 1205 also being connected to the bus 1204. The electronic device 1200 may also include one or more of the following components connected to the I/O interface 1205: an input section 1206 including a keyboard, a mouse, and the like; an output portion 1207 including a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, a speaker, and the like; a storage section 1208 including a hard disk or the like; and a communication section 1209 including a network interface card such as a LAN card, a modem, or the like. The communication section 1209 performs communication processing via a network such as the internet. The 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, or the like is installed as needed on the drive 1210 so that a computer program read out therefrom is installed into the storage section 1208 as needed.

According to embodiments of the present disclosure, the method flow according to embodiments of the present disclosure may be implemented as a computer software program. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable storage medium, the computer program comprising program code for performing the method shown in the flowcharts. In such an embodiment, the computer program can be downloaded and installed from a network via the communication portion 1209, and/or installed from the removable media 1211. The above-described functions defined in the system of the embodiments of the present disclosure are performed when the computer program is executed by the processor 1201. The systems, devices, apparatus, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the disclosure.

The present disclosure also provides a computer-readable storage medium that may be embodied in the apparatus/device/system described in the above embodiments; or may exist alone without being assembled into the apparatus/device/system. The computer-readable storage medium carries one or more programs which, when executed, implement methods in accordance with embodiments of the present disclosure.

According to embodiments of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium. Examples may include, but are not limited to: a portable computer diskette, 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 disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this disclosure, a computer-readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

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

Embodiments of the present disclosure also include a computer program product comprising a computer program containing program code for performing the method provided by the embodiments of the present disclosure, the program code for causing an electronic device to implement the method for processing a gateway service request, and the method for managing a cloud native gateway system provided by the embodiments of the present disclosure, when the computer program product is run on the electronic device.

The above-described functions defined in the system/apparatus of the embodiments of the present disclosure are performed when the computer program is executed by the processor 1201. The systems, apparatus, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the disclosure.

In one embodiment, the computer program may be based on a tangible storage medium such as an optical storage device, a magnetic storage device, or the like. In another embodiment, the computer program can also be transmitted, distributed over a network medium in the form of signals, and downloaded and installed via a communication portion 1209, and/or from a removable medium 1211. The computer program may include program code that may be transmitted using any appropriate network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.

According to embodiments of the present disclosure, program code for performing computer programs provided by embodiments of the present disclosure may be written in any combination of one or more programming languages, and in particular, such computer programs may be implemented in high-level procedural and/or object-oriented programming languages, and/or assembly/machine languages. Programming languages include, but are not limited to, such as Java, c++, python, "C" or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of remote computing devices, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., connected via the Internet using an Internet service provider).

The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions. Those skilled in the art will appreciate that the features recited in the various embodiments of the disclosure and/or in the claims may be combined in various combinations and/or combinations, even if such combinations or combinations are not explicitly recited in the disclosure. In particular, the features recited in the various embodiments of the present disclosure and/or the claims may be variously combined and/or combined without departing from the spirit and teachings of the present disclosure. All such combinations and/or combinations fall within the scope of the present disclosure.

The embodiments of the present disclosure are described above. However, these examples are for illustrative purposes only 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 embodiments cannot be used advantageously in combination. The scope of the disclosure is defined by the appended claims and equivalents thereof. Various alternatives and modifications can be made by those skilled in the art without departing from the scope of the disclosure, and such alternatives and modifications are intended to fall within the scope of the disclosure.

Claims

1. A method for processing a gateway service request, comprising:

in response to receiving a gateway service request to be processed, determining target gateway cluster information corresponding to a target gateway, target gateway information corresponding to a target gateway and target service information corresponding to a target service according to a preset mapping relation and the gateway service configuration information to be processed in the gateway service request to be processed;

determining respective running states 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 in at least one container group according to the respective running states of the at least one container group corresponding to the target service; and

2. The method of claim 1, wherein the determining, in response to receiving the pending gateway service request, target gateway cluster information corresponding to a target gateway, target gateway information corresponding to a target gateway, and target service information corresponding to a target service according to a preset mapping relationship and pending gateway service configuration information in the pending gateway service request comprises:

3. The method of claim 2, wherein the target gateway cluster comprises at least one gateway, each of the at least one gateway corresponding to at least one service, each of the at least one gateway corresponding to gateway address information, each of the at least one service corresponding to service port information;

the determining gateway address information corresponding to the target gateway and service port information corresponding to the target service according to the target gateway cluster information includes:

determining a 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,

and determining the service port information of the service corresponding to the gateway according to the gateway address information corresponding to the gateway.

4. The method of claim 2, wherein the determining target virtual internet protocol address information from the pending gateway service configuration information in response to receiving the pending gateway service request comprises:

5. The method of claim 2, wherein the second preset mapping relationship includes at least one second key-value relationship, the second key-value relationship including second key information and second value information, the at least one second key-value relationship being constructed by:

for each of the at least one second key-value relationship,

responding to the received gateway creation instruction, and acquiring a gateway identifier, gateway configuration information and a gateway cluster identifier;

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

determining the gateway address information as the second key information;

6. The method of claim 5, wherein, in the case where the target routing protocol is a border gateway protocol,

the determining gateway address information corresponding to the gateway identifier according to the target routing protocol and the virtual network address information comprises:

and according to the border gateway protocol, issuing the target address information through any two front-end agents so as to determine the target address information as the gateway address information.

7. The method of claim 5, wherein, in the case where the target routing protocol is an equal cost multi-path routing protocol,

and determining the equivalent routing information as the gateway address information.

8. The method of claim 2, wherein the third preset mapping relationship comprises at least one third key value relationship comprising third key information and third value information, the at least one third key value relationship being constructed by:

for each of the at least one third key value relationship,

in response to receiving a service creation instruction, acquiring a service identifier, service configuration information and a gateway identifier;

determining gateway address information corresponding to the gateway identification according to the gateway identification;

determining the service port information as the third key information;

and constructing the third key value relation according to the third key information and the third value information.

9. The method of any of claims 1 to 8, wherein the target service information includes container group address information corresponding to each of the at least one container group;

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 includes:

for each of the at least one container group address information,

establishing a detection network connection with the container group according to the address information of the container group;

10. The method of claim 9, wherein said determining the target container group among the at least one container group according to the respective operational states of the at least one container group corresponding to the target service comprises:

11. The method of any of claims 1-8, wherein the sending the pending gateway service request to the target set of containers comprises:

and sending the gateway service request to be processed to the target container group based on the actual network connection.

12. A method of managing a cloud native gateway system, comprising:

processing a target gateway service request by using the method of any one of claims 1 to 11 to obtain a processing result, wherein the target gateway service request comprises target gateway service configuration information, and the target gateway service configuration information is associated with a cloud native gateway system; and

13. A gateway service request processing apparatus, comprising:

The second determining module is used for determining the respective running states 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 in the at least one container group according to respective operation states of the at least one container group corresponding to the target service; and

14. A management device of a cloud native gateway system, comprising:

a processing module, configured to process a target gateway service request by using the apparatus of claim 13, to obtain a processing result, where 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

15. An electronic device, comprising:

one or more processors;

A memory for storing one or more instructions,

wherein the one or more instructions, when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1 to 11 or claim 12.

16. A computer readable storage medium having stored thereon executable instructions which when executed by a processor cause the processor to implement the method of any one of claims 1 to 11 or claim 12.

17. A computer program product comprising computer executable instructions for implementing the method of any one of claims 1 to 11 or claim 12 when executed.