Cloud service platform, cloud service deployment method and device

Abstract

The present application relates to a cloud service platform, a cloud service deployment method and an apparatus, the method comprising: in response to a cloud service deployment request from a client, deploying the cloud service under a first private network to which the cloud service platform belongs, and creating a service object for the cloud service; creating a first load balancer for the service object under the first private network to expose the cloud service to the outside through load balancing access; creating a second load balancer under a second private network to which the client belongs; establishing a private connection between the first load balancer and the second load balancer to enable the client to access the cloud service. In this way, it is possible to deploy cloud services under the private network to which the cloud service platform belongs. Since it is convenient to use security combination networks, ACLs, etc. to achieve multi-layer security protection under the private network, the cloud service deployed under the private network has higher security and can avoid performance loss caused by the cloud service host machine needing to bear the network security protection work.

Description

Technical Field

[0001] The present application relates to the field of cloud services, and in particular to a cloud service platform, a cloud service deployment method and a device. Background Art

[0002] Currently, after receiving a cloud service deployment request from a client, the cloud service platform will deploy the corresponding cloud service in the intranet environment of the cloud service platform.

[0003] The above process has the following two defects. On the one hand, since cloud services are deployed in an intranet environment, when implementing network-related functions such as security groups, the implementation method needs to be placed on the host machine of the cloud service. This will require the host machine of the cloud service to bear part of the network security protection work, resulting in a certain loss of host machine performance; on the other hand, in an intranet environment, the isolation between cloud services is not very good. When a machine in the intranet environment is invaded, it is very likely that other cloud services in the intranet environment will also be attacked. Summary of the Invention

[0004] In order to solve the above technical problems or at least partially solve the above technical problems, the present application provides a cloud service platform, a cloud service deployment method and an apparatus.

[0005] In a first aspect, the present application provides a cloud service deployment method, the method comprising:

[0006] In response to a cloud service deployment request from a client, deploy the cloud service in a first private network to which the cloud service platform belongs, and create a service object for the cloud service;

[0007] Creating a first load balancer for the service object in the first private network, so as to access and expose the cloud service externally through the first load balancer;

[0008] Creating a second load balancer in the second private network to which the client belongs;

[0009] A connection is established between the first load balancer and the second load balancer to enable the client to access the cloud service.

[0010] In a possible implementation, deploying the cloud service in the first private network to which the cloud service platform belongs includes:

[0011] Deploying a group of Pod containers on a first private network of the cloud service platform using a container orchestration engine tool, wherein the Pod containers are distributed on the same or different container orchestration engine nodes on the first private network;

[0012] A component of the cloud service is created in each of the Pod containers, where the component is used to implement and run the cloud service.

[0013] In a possible implementation, the creating the service object of the cloud service includes:

[0014] Create a service object;

[0015] The tag selector of the service object is pointed to the tag of the cloud service to bind the cloud service to the service object.

[0016] In one possible implementation, the method further includes:

[0017] Mapping the first access path of the host machine where the Pod container is located with the second access path of the Pod container; wherein the access path includes an IP address and a port number;

[0018] The step of creating a first load balancer for the service object in the first private network includes:

[0019] Setting the type of the service object to load balancing;

[0020] In response to the type of the service object being set to load balancing, creating a first load balancer;

[0021] The listener of the first load balancer is pointed to the first access path, so that when the first load balancer receives access traffic to the cloud service, the access traffic is forwarded to the host machine according to the first access path, and the host machine forwards the access traffic to the Pod container according to a second access path mapped to the first access path.

[0022] In one possible implementation, the method further includes:

[0023] The first load balancer is configured to disable a session persistence function.

[0024] In a second aspect, the present application provides a cloud service platform, wherein the cloud service platform is deployed in a first proprietary network;

[0025] After receiving the cloud service deployment request from the client, the cloud service platform executes the method as described in any one of the first aspects.

[0026] In one possible implementation, the cloud service platform uses a container orchestration engine system as a framework structure.

[0027] In a third aspect, the present application provides a cloud service deployment device, the device comprising:

[0028] A service deployment module, configured to deploy the cloud service in the first proprietary network of the cloud service platform in response to a cloud service deployment request from a client;

[0029] A service creation module, configured to create a service object for the cloud service;

[0030] A first load balancing module, configured to create a first load balancer for the service object under the first proprietary network, so as to expose the cloud service externally through the first load balancer;

[0031] A second load balancing module, configured to create a second load balancer under the second private network of the client;

[0032] A connection module is used to establish a private connection between the first load balancer and the second load balancer so that the client under the second private network can access the cloud service deployed under the first private network.

[0033] In a fourth aspect, the present application provides an electronic device, comprising a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other via the communication bus;

[0034] Memory for storing computer programs;

[0035] The processor is configured to implement the steps of the cloud service deployment method described in any one of the first aspects when executing the program stored in the memory.

[0036] In a fifth aspect, the present application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the cloud service deployment method as described in any one of the first aspects.

[0037] The above technical solution provided by the embodiment of the present application has the following advantages compared with the prior art:

[0038] The technical solution provided in the embodiment of the present application deploys a cloud service under the first VPC to which the cloud service platform belongs, and creates a Service object of the cloud service in response to a cloud service deployment request from a client. Under the first VPC, a first load balancer is created for the Service object to expose the cloud service to the outside through load balancing access, thereby realizing the deployment of the cloud service. Moreover, compared with the prior art of deploying cloud services in the intranet environment of the cloud service platform, deploying cloud services under the VPC to which the cloud service platform belongs, because under the VPC, security combination networks, ACLs, etc. can be conveniently used to achieve multi-layer security protection, the cloud service deployed under the VPC has higher security and can avoid performance loss caused by the cloud service host machine needing to bear the network security protection work. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.

[0040] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0041] Figure 1 A flowchart of a cloud service deployment method provided in an embodiment of the present application;

[0042] Figure 2 A schematic diagram of a cloud service platform system architecture implemented based on the cloud service deployment method provided in an embodiment of the present application;

[0043] Figure 3 A schematic diagram of a cloud service deployment device provided in an embodiment of the present application;

[0044] Figure 4 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0045] To make the purpose, technical solutions, and advantages of the embodiments of this application more clear, the technical solutions in the embodiments of this application will be clearly and completely described below in conjunction with the drawings in the embodiments of this application. Obviously, the described embodiments are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0046] To facilitate understanding of the embodiments of the present application, the following first explains the concepts and terms involved in the embodiments of the present application:

[0047] 1. Private Network

[0048] A Virtual Private Cloud (VPC) is a custom, logically isolated network space within a public cloud. Hosted within a VPC are user resources on the private cloud, such as physical cloud machines, cloud hosts, and cloud databases. Within a VPC, users can customize network segmentation, IP addresses, and routing policies, and implement multi-layered security through secure network configurations and ACLs (Access Control Lists). This demonstrates the increased flexibility and security offered by VPC.

[0049] Container Orchestration Engine

[0050] Kubernetes (K8s) is an open-source container orchestration engine developed by Google. It supports automated deployment, large-scale scalability, and containerized application management. In Kubernetes, users can create multiple containers, each running an application instance. Built-in load balancing policies enable management, discovery, and access to these application instances, eliminating the need for complex manual configuration and management by operations personnel.

[0051] Pod

[0052] A Pod is the smallest and simplest basic unit created or deployed in Kubernetes. A Pod can be considered a container or a combination of multiple containers. Containers within a Pod share container storage, networking, and runtime configuration. Each Pod corresponds to an image and runs as a microservice module. In Kubernetes, a single application (or service) instance may consist of a single Pod or resources shared by multiple Pods.

[0053] 4. Service Object (also called Service Object)

[0054] Because Pods are temporary, the IP and port numbers of Pods corresponding to applications (or services) also change dynamically. Therefore, when a group of Pods acts as a service provider, the caller needs to automatically be aware of the service provider. Based on this, the Service mechanism was introduced.

[0055] The Service object abstracts the access policy for a group of Pods, shields the dynamic changes of backend instances and load balancing across multiple instances, and is used to manage service access in the cluster.

[0056] 5. Private Link

[0057] Private connections enable VPCs to establish secure and stable private connections with cloud services, simplifying network architecture and enabling private network access services.

[0058] When accessing cloud services through a private connection, you can add security group rules to the elastic network interface cards (ENICs) used to access services in the VPC network, providing stronger security and control measures.

[0059] Based on the explanation of the above-mentioned conceptual terms, a cloud service deployment method provided by an embodiment of the present application is explained below through specific examples. The examples do not constitute a limitation of the present application.

[0060] See also Figure 1 , is a flow chart of a cloud service deployment method provided in an embodiment of the present application. Figure 1 As shown, the following steps are included:

[0061] Step 101: In response to a cloud service deployment request from a client, deploy a cloud service under a first VPC to which a cloud service platform belongs.

[0062] Cloud service refers to obtaining required services through the Internet in an on-demand and easily scalable manner. Simply put, cloud service can put the software, hardware, and data required by users on the Internet, and use different IT devices to connect with each other at any time and place to achieve data access, computing and other purposes.

[0063] As an example, in an application, when a client needs to deploy a cloud service on a cloud service platform, it may send a cloud service deployment request to the cloud service platform to request the deployment of the cloud service. The specific content of the cloud service deployment request may include, but is not limited to, the memory space required for deploying the cloud service, the number of CPUs, the number of disks, the number of nodes, etc.

[0064] In this embodiment, unlike the prior art, after receiving the cloud service deployment request, the cloud service platform deploys the cloud service in the VPC to which the cloud service platform belongs (hereinafter referred to as the first VPC for ease of description). Because VPCs facilitate the use of security composite networks, ACLs, and other multi-layered security protections, cloud services deployed in VPCs have a higher level of security.

[0065] As an example, a cloud service platform uses the Kubernetes container orchestration engine system as its framework and is deployed within a first VPC. Based on this, when deploying cloud services within the first VPC, the cloud service platform can use Kubernetes to deploy a set of Pod containers within the first VPC. These Pod containers are distributed across the same or different Kubernetes nodes within the first VPC, and then the components required to run the cloud service are created within each Pod container. In this way, cloud services are deployed within the first VPC of the cloud service platform.

[0066] Furthermore, when the group of Pod containers is distributed across different Kubernetes nodes in the first VPC, the group of Pod containers can be distributed across Kubernetes nodes in different availability zones in the first VPC. Specifically, when deploying a group of Pod containers in the first VPC, weights can be set for Kubernetes nodes in different availability zones based on affinity and anti-affinity policies, thereby controlling the availability zones and Kubernetes nodes where the deployed Pods are located.

[0067] It is understandable that by deploying a group of Pod containers in different availability zones, it is possible to ensure that the overall availability of the cloud service is not affected when a single availability zone fails, thereby achieving multi-availability zone level high availability of the cloud service.

[0068] It should be noted here that the embodiment of the present application uses Kubernetes' container service to provide functions such as creation and management of cloud services. Compared with the Nova component based on OpenStack to provide functions such as creation and management of cloud services, it is more convenient to use and closer to cloud native.

[0069] For a better understanding, the following uses the TiDB database (an open source distributed relational database) cloud service as an example to illustrate the specific implementation of step 101:

[0070] The basic components of the TiDB database include the tidb Pod, the tikv Pod, and the pd Pod. The tidb Pod provides data access services to customers, the tikv Pod is responsible for data storage services, and the pd Pod is responsible for recording metadata. Therefore, in step 101, when deploying the TiDB database service, the cloud service platform can use Kubernetes to deploy a set of Pod containers under the first VPC. This set of Pod containers includes three Pod containers, and the three components mentioned above are created in each of these three Pod containers.

[0071] Step 102: Create a Service object for the cloud service.

[0072] In Kubernetes, Service objects use label selectors to locate backend Pod containers, which host cloud services. Therefore, using label selectors to locate backend Pod containers is equivalent to binding the Service object to the cloud service through the label selector. Therefore, in step 102, a Service object is first created, and then the Service object's label selector is pointed to the cloud service's label to bind the cloud service to the Service object.

[0073] In addition, in an embodiment of the present application, after creating the Service object of the cloud service, a routing table will also be created in order to ensure that traffic from the external network accessing the cloud service can be forwarded to the Pod container corresponding to the cloud service.

[0074] As an embodiment, when the Service object is configured in Local mode, in the above-mentioned routing table, the access path of the host machine where the Pod container is located (hereinafter referred to as the first access path) and the access path of the Pod container (hereinafter referred to as the second access path) are mapped, wherein the access path includes the IP address and port number, that is, the first access path includes the IP address and port number of the host machine, and the second access path includes the IP address and port number of the Pod container.

[0075] The port number of the host is uniformly allocated by Kubernetes. Specifically, Kubernetes searches for an unoccupied port on the host as the host port here.

[0076] The IP address of the Pod container is allocated from the podCIDR assigned to each Kubernetes node by Kube-controller-manager when the Pod container is deployed through Kubernetes. Since the podCIDR on all Kubernetes nodes is a disjoint subnet, it allows each Pod container to be assigned a unique IP address.

[0077] The port number of the Pod container is set when the cloud service is created based on the configuration information in the specified configuration file.

[0078] As another embodiment, when the Service object is configured in Cluster mode, the access path of the Service object (hereinafter referred to as the third access path) is mapped to the second access path of the Pod container in the above-mentioned routing table. The access path of the Service object refers to the Cluster IP address and port number of the Service object. In practice, the above-mentioned mapping of the third access path of the Service object and the second access path of the Pod container is achieved by creating the second access path of the Pod container in the Endpoints resource object of the Service object.

[0079] The Cluster IP address of the Service object is assigned by Kubernetes. Specifically, Kubernetes selects an IP address from the IP network segment configured when the Service object is created and assigns it to the Service object.

[0080] The port number of the Service object is set when the Service object is created based on the configuration information in the specified configuration file.

[0081] Step 103: Create a first load balancer for the Service object under the first VPC to expose the cloud service externally through the first load balancer.

[0082] Those skilled in the art will appreciate that Service objects have multiple types, namely ServiceType, and the ServiceType of a Service object determines how it exposes its service. In the embodiment of the present application, the cloud service is exposed to the outside through load balancing access.

[0083] Based on this, in this step 103, the type of the Service object is set to LoadBalancer (i.e., load balancing). In response to the type of the Service object being set to LoadBalancer, a load balancer (hereinafter referred to as the first load balancer) is created for the Service object under the first VPC. Then, the listener of the first load balancer is pointed to the first access path. At this point, the cloud service is exposed to the outside in a load balancing manner through the first load balancer.

[0084] In addition, in an embodiment of the present application, after creating the first load balancer, the first load balancer can be set to disable the session persistence function and the type of the first load balancer can be set to intranet load balancing. By setting the first load balancer to disable the session persistence function, the problem of the same IP address always accessing the same backend service can be solved. By setting the type of the first load balancer to intranet load balancing, cloud services can be exposed to the client's VPC environment.

[0085] Step 104: Create a second load balancer in the second VPC to which the client belongs.

[0086] In step 104, a load balancer (hereinafter referred to as the second load balancer) is first created under the terminal subnet of the second VPC to which the client belongs, and then the second load balancer is configured. Here, configuring the second load balancer includes but is not limited to: configuring the VPC ID of the second load balancer, the terminal subnet ID, etc.

[0087] Step 105: Establish a connection between the first load balancer and the second load balancer to enable the client to access the cloud service.

[0088] In this embodiment of the present application, establishing a connection between the first load balancer and the second load balancer means opening a communication "bridge" between the first VPC and the second VPC, allowing clients in the second VPC to access cloud services deployed in the first VPC. Optionally, the above connection is a private connection.

[0089] Furthermore, when a private connection is established between the first load balancer and the second load balancer, the second load balancer is set as the client end of the private connection, and the first load balancer is set as the server end of the private connection, so that the client under the second VPC can unidirectionally access the cloud service deployed under the first VPC.

[0090] Specifically, when a client initiates access traffic to a cloud service, the access traffic is first sent from the client to the second load balancer. The second load balancer then forwards the access traffic to the first load balancer via the private connection. Subsequently, upon receiving the access traffic to the cloud service, the first load balancer first forwards the access traffic to the physical machine according to the first access path. The physical machine then forwards the access traffic to the Pod container according to the second access path mapped to the first access path. This enables clients in the second VPC to access the cloud service deployed in the first VPC.

[0091] See also Figure 2 , which is a schematic diagram of a cloud service platform system architecture implemented based on the cloud service deployment method provided in an embodiment of the present application.

[0092] like Figure 2 As shown, the cloud service platform system architecture includes a cloud service platform 11 and a client 12. The cloud service platform 11 adopts the Kubernetes container orchestration engine system as a framework structure and is deployed in a first VPC 13. The client 12 is deployed in a second VPC 14.

[0093] Using the technical solutions provided in the embodiments of the present application, when client 12 sends a cloud service deployment request to cloud service platform 11, cloud service platform 11 deploys the cloud service in the computing resources of first VPC 13. Specifically, the cloud service platform uses the Kubernetes tool to deploy a set of Pod containers in first VPC 13, creating the components required to run the cloud service in each Pod container to implement the deployment of the cloud service in first VPC 13. Here, the computing resources of first VPC 13 may include cloud physical machines and cloud hosts.

[0094] Cloud service platform 11 then creates a Service object for the deployed cloud service in first VPC 13 and exposes the deployed cloud service by creating a first load balancer 15 for the Service object. Cloud service platform 11 then creates a second load balancer 16 in second VPC 14 and establishes a private connection between second load balancer 16 and first load balancer 15. Second load balancer 16 is configured as the client end of the private connection, while first load balancer 15 is configured as the server end of the private connection. This allows client 12 to unidirectionally access the cloud service deployed in first VPC 13.

[0095] The technical solution provided in the embodiment of the present application deploys a cloud service under the first VPC to which the cloud service platform belongs, and creates a Service object of the cloud service in response to a cloud service deployment request from a client. Under the first VPC, a first load balancer is created for the Service object to expose the cloud service to the outside through load balancing access, thereby realizing the deployment of the cloud service. Moreover, compared with the prior art of deploying cloud services in the intranet environment of the cloud service platform, deploying cloud services under the VPC to which the cloud service platform belongs, because under the VPC, security combination networks, ACLs, etc. can be conveniently used to achieve multi-layer security protection, the cloud service deployed under the VPC has higher security and can avoid performance loss caused by the cloud service host machine needing to bear the network security protection work.

[0096] Figure 3 This is a schematic diagram of a cloud service deployment device provided in an embodiment of the present application. Figure 3 As shown, the device includes: a service deployment module 31, a service creation module 32, a first load balancing module 33, a second load balancing module 34, and a connection module 35.

[0097] The service deployment module 31 is configured to deploy the cloud service in the first proprietary network of the cloud service platform in response to a cloud service deployment request from a client;

[0098] A service creation module 32 is used to create a service object of the cloud service;

[0099] A first load balancing module 33 is configured to create a first load balancer for the service object under the first private network, so as to expose the cloud service externally through the first load balancer;

[0100] A second load balancing module 34 is configured to create a second load balancer under the second private network of the client;

[0101] The connection module 35 is used to establish a connection between the first load balancer and the second load balancer so that the client under the second private network can access the cloud service deployed under the first private network.

[0102] In a possible implementation, the service deployment module 31 is specifically configured to:

[0103] Deploying a group of Pod containers on a first private network to which the cloud service platform belongs using a container orchestration engine tool, wherein the Pod containers are distributed on the same or different container orchestration engine nodes on the first private network;

[0104] A component of the cloud service is created in each of the Pod containers, where the component is used to implement and run the cloud service.

[0105] In a possible implementation, the service creation module 32 is specifically configured to:

[0106] Create a service object; point the label selector of the service object to the label of the cloud service to bind the cloud service to the service object.

[0107] In a possible embodiment, the device further includes (not shown in the figure):

[0108] A mapping module is used to map a first access path of the host machine where the Pod container is located with a second access path of the Pod container; wherein the access path includes an IP address and a port number;

[0109] The first load balancing module 33 is specifically configured to:

[0110] The type of the service object is set to load balancing; in response to the type of the service object being set to load balancing, a first load balancer is created; and a listener of the first load balancer is pointed to the first access path, so that when the first load balancer receives access traffic to the cloud service, the access traffic is forwarded to the host machine according to the first access path, and the host machine then forwards the access traffic to the Pod container according to a second access path mapped to the first access path.

[0111] In a possible embodiment, the device further includes (not shown in the figure):

[0112] A setting module is used to set the first load balancer to disable the session persistence function.

[0113] like Figure 4As shown, an embodiment of the present application provides an electronic device, including a processor 411, a communication interface 412, a memory 413 and a communication bus 414, wherein the processor 411, the communication interface 412, and the memory 413 communicate with each other through the communication bus 414.

[0114] Memory 413, for storing computer programs;

[0115] In one embodiment of the present application, the processor 411 is configured to execute a program stored in the memory 413 to implement the cloud service deployment method provided by any of the aforementioned method embodiments, including:

[0116] In response to a cloud service deployment request from a client, deploy the cloud service in a first private network to which the cloud service platform belongs, and create a service object for the cloud service;

[0117] Creating a first load balancer for the service object in the first private network to expose the cloud service externally through the first load balancer;

[0118] Creating a second load balancer in the second private network to which the client belongs;

[0119] A connection is established between the first load balancer and the second load balancer to enable the client to access the cloud service.

[0120] An embodiment of the present application also provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the steps of the cloud service deployment method provided in any of the aforementioned method embodiments are implemented.

[0121] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article, or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or device. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of other identical elements in the process, method, article, or device comprising the element.

[0122] The foregoing description is intended only to provide specific embodiments of the present invention, which will enable those skilled in the art to understand and implement the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention is not intended to be limited to the embodiments shown herein, but is intended to be accorded the widest scope consistent with the principles and novel features claimed herein.

Claims

1. A cloud service deployment method, characterized in that: The method comprises: In response to a cloud service deployment request from a client, deploy the cloud service in a first private network to which the cloud service platform belongs, and create a service object for the cloud service; Creating a first load balancer for the service object in the first private network to expose the cloud service externally through the first load balancer; Creating a second load balancer under a second private network to which the client belongs, wherein the first private network and the second private network provide multi-layer security protection through security groups and access control lists; A private connection is established between the first load balancer and the second load balancer to enable the client to access the cloud service, wherein the private connection is a unidirectional channel that allows access traffic to pass from the second load balancer to the first load balancer.

2. The method according to claim 1, characterized in that The deploying of the cloud service in the first proprietary network to which the cloud service platform belongs includes: Deploying a group of Pod containers on a first private network to which the cloud service platform belongs using a container orchestration engine tool, wherein the Pod containers are distributed on the same or different container orchestration engine nodes on the first private network; A component of the cloud service is created in each of the Pod containers, where the component is used to implement and run the cloud service.

3. The method according to claim 2, characterized in that The step of creating a service object for the cloud service includes: Create a service object; The tag selector of the service object is pointed to the tag of the cloud service to bind the cloud service to the service object.

4. The method according to claim 3, characterized in that The method further comprises: Mapping the first access path of the host machine where the Pod container is located with the second access path of the Pod container; wherein the access path includes an IP address and a port number; The step of creating a first load balancer for the service object in the first private network includes: Setting the type of the service object to load balancing; In response to the type of the service object being set to load balancing, creating a first load balancer; The listener of the first load balancer is pointed to the first access path, so that when the first load balancer receives access traffic to the cloud service, the access traffic is forwarded to the host machine according to the first access path, and the host machine forwards the access traffic to the Pod container according to a second access path mapped to the first access path.

5. The method according to claim 4, characterized in that The method further comprises: The first load balancer is configured to disable a session persistence function.

6. A cloud service platform, characterized in that: The cloud service platform is deployed in a first proprietary network; After receiving the cloud service deployment request from the client, the cloud service platform executes the method according to any one of claims 1 to 5.

7. The cloud service platform according to claim 6, characterized in that: The cloud service platform uses a container orchestration engine system as its framework structure.

8. A cloud service deployment device, characterized in that: The device comprises: A service deployment module, configured to deploy the cloud service in the first proprietary network of the cloud service platform in response to a cloud service deployment request from a client; A service creation module, configured to create a service object for the cloud service; A first load balancing module is configured to create a first load balancer for the service object under the first proprietary network, so as to expose the cloud service externally through a load balancing access mode; A second load balancing module, configured to create a second load balancer under a second private network of the client, wherein the first private network and the second private network provide multi-layer security protection through security groups and access control lists; A connection module is configured to establish a private connection between the first load balancer and the second load balancer, so that the client in the second private network can access the cloud service deployed in the first private network, wherein the private connection is a unidirectional channel that allows access traffic to pass from the second load balancer to the first load balancer.

9. An electronic device, characterized in that: It includes a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus; Memory for storing computer programs; The processor is configured to implement the steps of the cloud service deployment method according to any one of claims 1 to 5 when executing the program stored in the memory.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the cloud service deployment method according to any one of claims 1 to 5 are implemented.

Images