CN114070889B - Configuration method, traffic forwarding device, storage medium, and program product - Google Patents
Configuration method, traffic forwarding device, storage medium, and program product Download PDFInfo
- Publication number
- CN114070889B CN114070889B CN202111327832.0A CN202111327832A CN114070889B CN 114070889 B CN114070889 B CN 114070889B CN 202111327832 A CN202111327832 A CN 202111327832A CN 114070889 B CN114070889 B CN 114070889B
- Authority
- CN
- China
- Prior art keywords
- cluster
- traffic
- application
- configuration file
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 59
- 238000012360 testing method Methods 0.000 claims description 48
- 238000005516 engineering process Methods 0.000 abstract description 8
- 238000010586 diagram Methods 0.000 description 18
- 238000004590 computer program Methods 0.000 description 14
- 101100264195 Caenorhabditis elegans app-1 gene Proteins 0.000 description 12
- 238000012545 processing Methods 0.000 description 10
- 238000004891 communication Methods 0.000 description 8
- 230000006870 function Effects 0.000 description 5
- 230000008569 process Effects 0.000 description 4
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 101100491335 Caenorhabditis elegans mat-2 gene Proteins 0.000 description 2
- 102100033121 Transcription factor 21 Human genes 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000011084 recovery Methods 0.000 description 2
- 239000000725 suspension Substances 0.000 description 2
- 101150109289 tcf21 gene Proteins 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 238000013473 artificial intelligence Methods 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000012512 characterization method Methods 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000005315 distribution function Methods 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000010801 machine learning Methods 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000001953 sensory effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The configuration method, the flow forwarding method, the equipment, the storage medium and the program product provided by the disclosure relate to an application deployment technology, and the scheme comprises the steps of obtaining a configuration file corresponding to an application to be deployed and a preset cluster list; the configuration information is used for indicating a flow distribution rule, the cluster list comprises cluster information, and nodes in a cluster indicated by the cluster information are used for deploying the application; generating an inlet controller according to the configuration file and cluster information contained in a cluster table; the ingress controller is configured to receive the traffic and forward the traffic to a destination node of a destination cluster corresponding to the traffic, where the destination cluster is any one of the clusters. In the embodiment, the inlet controllers independent of the clusters are arranged, so that the flow can be controlled according to the unified rule, the flow can be forwarded in a unified way, and the requirement of a user on unified management of the flow of the access multiple clusters can be met.
Description
Technical Field
The present disclosure relates to application deployment technology in computer technology, and in particular, to a configuration method, a traffic forwarding method, a device, a storage medium, and a program product.
Background
With the development and popularization of container technology, container technology taking Kubernetes as a standard has become a cloud computing fact standard.
In the service form and the cloud disaster recovery scenario, multiple regions are required to be deployed for the service, for example, the same service is deployed in a plurality of clusters, and when the service of one cluster is down, the traffic can be quickly migrated to other clusters, so that the service availability is ensured.
In the prior art, various schemes for managing the deployment of the Kubernetes application under multiple clusters exist, and when the schemes manage the deployment of the Kubernetes application under multiple clusters, the schemes do not support the access of traffic rules across multiple clusters, so that traffic cannot be controlled to access each cluster according to the unified rules.
Disclosure of Invention
The disclosure provides a configuration method, a traffic forwarding method, a device, a storage medium and a program product, which solve the problem that traffic cannot be controlled to access each cluster according to a unified rule in the prior art.
According to a first aspect of the present disclosure, there is provided a method for configuring a plurality of clusters deployed with an application, including:
acquiring a configuration file corresponding to an application to be issued and a preset cluster list; the configuration information is used for indicating a flow distribution rule, the cluster list comprises cluster information, and nodes in a cluster indicated by the cluster information are used for deploying the application;
Generating an inlet controller according to the configuration file and cluster information contained in the cluster table; the ingress controller is configured to receive traffic and forward the traffic to a destination node of a destination cluster corresponding to the traffic, where the destination cluster is any one of the clusters.
According to a second aspect of the present disclosure, there is provided a traffic forwarding method in a multi-cluster scenario, including:
receiving a flow, and analyzing the flow;
if the flow comprises the test parameters, determining a first target cluster provided with the test node and the test node deployed with the test version application in a plurality of clusters according to a preset inlet controller;
forwarding the traffic to a test node of the first destination cluster.
According to a third aspect of the present disclosure, there is provided a configuration apparatus of a multi-cluster deployed with an application, comprising:
the acquisition unit is used for acquiring a configuration file corresponding to the application to be distributed and a preset cluster list; the configuration information is used for indicating a flow distribution rule, the cluster list comprises cluster information, and nodes in a cluster indicated by the cluster information are used for deploying the application;
The controller generating unit is used for generating an inlet controller according to the configuration file and cluster information contained in the cluster table; the ingress controller is configured to receive traffic and forward the traffic to a destination node of a destination cluster corresponding to the traffic, where the destination cluster is any one of the clusters.
According to a fourth aspect of the present disclosure, there is provided a traffic forwarding device in a multi-cluster scenario, including:
the receiving unit is used for receiving the flow and analyzing the flow;
the forwarding unit is used for determining a first target cluster provided with a test node and a test node deployed with a test version application in a plurality of clusters according to a preset inlet controller if the flow comprises the test parameters; forwarding the traffic to a test node of the first destination cluster.
According to a fifth aspect of the present disclosure, there is provided an electronic device comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of the first or second aspect.
According to a sixth aspect of the present disclosure, there is provided a non-transitory computer readable storage medium storing computer instructions for causing the computer to perform the method of the first or second aspect.
According to a seventh aspect of the present disclosure, there is provided a computer program product comprising: a computer program stored in a readable storage medium from which at least one processor of an electronic device can read, the at least one processor executing the computer program causing the electronic device to perform the method of the first or second aspect.
The configuration method, the traffic forwarding device, the storage medium and the program product provided by the disclosure comprise the steps of obtaining a configuration file corresponding to an application to be distributed and a preset cluster list; the configuration information is used for indicating a flow distribution rule, the cluster list comprises cluster information, and nodes in a cluster indicated by the cluster information are used for deploying the application; generating an inlet controller according to the configuration file and cluster information contained in a cluster table; the ingress controller is configured to receive the traffic and forward the traffic to a destination node of a destination cluster corresponding to the traffic, where the destination cluster is any one of the clusters. In the embodiment, the inlet controllers independent of the clusters are arranged, so that the flow can be controlled according to the unified rule, the flow can be forwarded in a unified way, and the requirement of a user on unified management of the flow of the access multiple clusters can be met.
It should be understood that the description in this section is not intended to identify key or critical features of the embodiments of the disclosure, nor is it intended to be used to limit the scope of the disclosure. Other features of the present disclosure will become apparent from the following specification.
Drawings
The drawings are for a better understanding of the present solution and are not to be construed as limiting the present disclosure. Wherein:
FIG. 1 is a system architecture diagram illustrating a multi-cluster deployed with applications, as shown in an exemplary embodiment;
FIG. 2 is a flow diagram illustrating a method of configuring a multi-cluster deployed with an application according to an exemplary embodiment of the present disclosure;
FIG. 3 is a system block diagram of a multi-cluster deployed with applications, as shown in an exemplary embodiment of the present disclosure;
FIG. 4 is a flow diagram illustrating a method of configuring a multi-cluster deployed with an application according to another exemplary embodiment of the present disclosure;
FIG. 5 is a system block diagram of a multi-cluster deployed with applications, as shown in another exemplary embodiment of the present disclosure;
fig. 6 is a flow chart of a flow forwarding method in a multi-cluster scenario according to an exemplary embodiment of the present disclosure;
FIG. 7 is a schematic diagram of a configuration device with multiple clusters of applications deployed, as shown in an exemplary embodiment of the present disclosure;
FIG. 8 is a schematic structural diagram of a multi-cluster configuration device with applications deployed, as shown in another exemplary embodiment of the present disclosure;
fig. 9 is a schematic structural diagram of a traffic forwarding device in a multi-cluster scenario according to an exemplary embodiment of the present disclosure;
fig. 10 is a block diagram of an electronic device for implementing the methods of embodiments of the present disclosure.
Detailed Description
Exemplary embodiments of the present disclosure are described below in conjunction with the accompanying drawings, which include various details of the embodiments of the present disclosure to facilitate understanding, and should be considered as merely exemplary. Accordingly, one of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present disclosure. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
FIG. 1 is a system architecture diagram illustrating a multi-cluster deployed with applications, according to an example embodiment.
As shown in fig. 1, a plurality of clusters 11 may be provided for service requirements or disaster recovery backup requirements, and applications may be deployed in each cluster 11. If the application deployment adopts the container technology, a container is set in the cluster, and the application is containerized.
In this system architecture, after the system receives traffic for accessing the application, the traffic is forwarded to one of the clusters 11 randomly through the intelligent DNS. An ingress controller (Ingress Controller) is provided in each cluster 11, and after traffic enters the clusters 11, the traffic is forwarded by the ingress controller in the cluster 11 to nodes (Pod) in the cluster 11.
However, this approach cannot set the access traffic rules across multiple clusters, and cannot control traffic access to each cluster according to a unified rule.
In order to solve the technical problem, in the scheme provided by the disclosure, an inlet controller independent of each cluster is provided, and the inlet controller can determine which cluster to forward the traffic to and which node of the cluster to forward the traffic to based on a preset traffic distribution rule, so that the accessed traffic can be uniformly forwarded, and the unified management of the traffic of multiple clusters with applications deployed by the access by the user is satisfied.
Fig. 2 is a flow chart illustrating a method of configuring a multi-cluster deployed with an application according to an exemplary embodiment of the present disclosure.
As shown in fig. 2, the configuration method of multiple clusters deployed with applications provided by the present disclosure includes:
Step 201, acquiring a configuration file corresponding to an application to be distributed and a preset cluster list; the configuration information is used for indicating a traffic distribution rule, the cluster list comprises cluster information, and nodes in the cluster indicated by the cluster information are used for deploying the application.
The scheme provided by the disclosure can be used in an application deployment platform, the deployment platform can be arranged in a cluster and also can be arranged in user equipment, and a user can operate in the platform to configure the cluster for deploying the application.
The applications deployed in the cluster may provide application services, and in particular, may be deployed in each node in the cluster. When a corresponding application program is set in the terminal equipment, the terminal equipment can use the function provided by the application service, specifically, the request sent by the terminal equipment can be distributed to the nodes of the cluster, the nodes process the request according to the deployed application, and the processing result is fed back to the terminal equipment.
In particular, when an application is deployed in multiple clusters, the clusters may be configured.
Further, when the multi-cluster is configured, a configuration file of the application to be distributed can be obtained, and the configuration information is used for indicating the traffic distribution rule. For example, forwarding traffic randomly, for example, forwarding traffic according to a load condition of the cluster, for example, forwarding traffic according to gray scale test information.
In practical application, the configuration file may be set by a user according to requirements, for example, may include a rule that traffic is forwarded to a cluster, and may also include a rule that after the traffic is forwarded to the cluster, the traffic is forwarded to a node in the cluster.
When the multi-cluster is configured, a preset cluster list corresponding to the application to be distributed can be obtained. The cluster list comprises cluster information, and nodes in the clusters indicated by the cluster information are used for deploying the application.
Specifically, the user may set a cluster list of the application to be published according to the requirement, where a plurality of cluster information, such as a cluster identifier, is recorded in the cluster list. For example, if the identification of the first cluster, the identification of the second cluster, and the identification of the third cluster are included in the cluster list, the characterization requires that the application to be deployed into the three clusters, and therefore, the three clusters need to be configured.
Step 202, generating an inlet controller according to the configuration file and cluster information included in a cluster table; the ingress controller is configured to receive the traffic and forward the traffic to a destination node of a destination cluster corresponding to the traffic, where the destination cluster is any one of the clusters.
Further, an ingress controller may be generated in the platform. After the application to be deployed is deployed, the ingress controller is configured to forward traffic of the application to a node in the cluster, so that the traffic is responded by the application deployed in the node.
In practical application, the inlet controller can be generated according to the configuration file and cluster information included in the cluster table. For example, the traffic distribution rule may be determined according to information in the configuration file, and the information of the clusters and nodes capable of receiving the traffic may be determined according to the cluster information, so that the ingress controller is generated according to the rules. The ingress controller can forward the received traffic to any cluster indicated by the cluster information according to the traffic distribution rule, and specifically to any node of the cluster where the application is deployed.
Fig. 3 is a system architecture diagram of a multi-cluster deployed with applications, as shown in an exemplary embodiment of the present disclosure.
As shown in fig. 3, there are a plurality of clusters 31 in the system architecture, each cluster includes a plurality of nodes, and applications are deployed in the nodes, for example, app1 may be deployed and App2 may also be deployed.
The method provided according to the present disclosure may generate an ingress controller from a deployed application.
In one embodiment, an ingress controller may be generated for forwarding traffic for App1, and an ingress controller may also be generated for forwarding traffic for App 2. After receiving the flow of App1, the system may forward the flow to the ingress controller 32 by the intelligent DNS, and then forward the flow to the node of the cluster by the ingress controller corresponding to App1, and after receiving the flow of App2, the system may forward the flow to the ingress controller corresponding to App2 by the intelligent DNS, and then forward the flow to the node of the cluster by the ingress controller corresponding to App 2.
In another embodiment, only one ingress controller may be generated, and the flow forwarding rule of each App may be written into the ingress controller, so that the ingress controller may perform forwarding processing on the flows according to the flow forwarding rule of each App.
The method for configuring the multi-cluster deployed with the application comprises the steps of obtaining a configuration file corresponding to the application to be deployed and a preset cluster list; the configuration information is used for indicating a flow distribution rule, the cluster list comprises cluster information, and nodes in a cluster indicated by the cluster information are used for deploying the application; generating an inlet controller according to the configuration file and cluster information contained in a cluster table; the ingress controller is configured to receive the traffic and forward the traffic to a destination node of a destination cluster corresponding to the traffic, where the destination cluster is any one of the clusters. In the embodiment, the inlet controllers independent of the clusters are arranged, so that the flow can be controlled according to the unified rule, the flow can be forwarded in a unified way, and the requirement of a user on unified management of the flow of the access multiple clusters can be met.
Fig. 4 is a flow diagram illustrating a method of configuring a multi-cluster deployed with an application according to another exemplary embodiment of the present disclosure.
As shown in fig. 4, the configuration method of multiple clusters deployed with applications provided by the present disclosure includes:
step 401, obtaining a preset cluster list corresponding to an application to be deployed.
Step 401 is similar to the manner of obtaining the cluster list in step 201, and will not be described again.
Step 402, obtaining a service configuration file and an entry configuration file corresponding to an application to be deployed, wherein the entry configuration file is a rule for distributing traffic to a cluster, and the service configuration file is a rule for forwarding traffic received by the cluster to nodes in the cluster.
When the cluster is configured, a service configuration file corresponding to the application to be distributed can be acquired, and the service configuration file is acquired. The service profile and the portal profile corresponding to the application to be deployed may be set in advance according to the requirements.
Specifically, the service profile may be, for example, service yaml, in which a rule for forwarding traffic received by the cluster to a node in the cluster is recorded, and the user may set the service profile according to the requirement.
Further, the entry profile may be, for example, ingress yaml, in which a rule is recorded that forwards the received traffic to any one of the clusters, and the user may set the entry profile according to the requirement.
In this embodiment, the user may set the traffic distribution rules according to the requirements, and then may generate the ingress controller according to the rules, where the ingress controller may forward the traffic according to the rules, so as to forward the traffic according to the unified rules.
Step 403, determining a traffic forwarding rule according to the rule of distributing traffic to the cluster and the rule of forwarding traffic received by the cluster to nodes in the cluster.
The platform can combine the rule that the traffic is distributed to the cluster and the rule that the traffic received by the cluster is forwarded to the nodes in the cluster to obtain the whole traffic forwarding rule.
For example, the rule for distributing traffic to clusters includes forwarding traffic to a first cluster when a first condition is satisfied. In a rule for forwarding traffic received by a cluster to nodes in the cluster, including when the second condition is satisfied, the traffic is forwarded to a first node in the cluster. Based on this, a traffic forwarding rule may be generated, which is forwarded to the first node of the first cluster when the traffic satisfies the first condition and the second condition.
Step 404, generating an entrance controller according to the traffic forwarding rule and the cluster information.
Specifically, after the platform determines the overall flow forwarding rule, the platform can generate the inlet controller according to the information of the clusters deployed according to the application needs.
Furthermore, the ingress controller may record the traffic forwarding rule of the application, and may record cluster information corresponding to the application, so that after the ingress controller receives the traffic of the application, the ingress controller may forward the traffic to any cluster corresponding to the application based on the recorded traffic forwarding rule.
In this embodiment, the platform can generate an ingress controller corresponding to the application, and then can perform unified forwarding processing on the traffic of the application through the ingress controller.
And step 405, according to the cluster list and the application to be published, acquiring each object configuration file corresponding to each cluster information included in the cluster list, wherein the object configuration files are files corresponding to both the clusters and the application.
In practical application, the platform may also obtain an object configuration file of the application to be published, and specifically may obtain each object configuration file corresponding to the cluster for deploying the application. For example, if an application needs to be deployed in a first cluster, a second cluster, and a third cluster, three object configuration files of the application may be obtained, where the three object configuration files respectively correspond to the first cluster, the second cluster, and the third cluster.
Wherein, an object configuration file can be preset for the cluster for deploying the application to be deployed. The object configuration file may be, for example, a replyment yaml, which is used to instruct the cluster to generate an object, and further manage applications deployed in the cluster through the object.
Specifically, when the object configuration file is acquired, a file template can be acquired first, and then the object configuration file can be obtained by adjusting the file template.
Further, a plurality of history object configuration files can be obtained, wherein the history object configuration files correspond to a plurality of clusters and applications; determining a file template in the history object configuration file according to the specified information; and modifying the file template according to the object configuration information corresponding to each preset cluster to obtain the object configuration file corresponding to each preset cluster.
When the application is actually applied, if the application to be distributed is an upgrade version of the existing application, the application has corresponding historical object configuration files when upgrading all versions of the existing application. For example, there is App1, when the App is first released, a first version is released, when the App1 of the version is released, a history object configuration file v1 needs to be set, when the App is second released, a second version is released, and when the App is released, a history object configuration file v2 needs to be set.
Thus, a plurality of history object profiles corresponding to the application to be deployed may be acquired, which may be files corresponding to the cluster in which the App is deployed. For example, a history object profile used when deployed in a first cluster, or a history object profile used when deployed in a second cluster.
Wherein, the specified information can be preset, and the specified information is used for determining the file template in the history object configuration file. For example, the user may preset a version identification for indicating which historical object configuration file is determined to be the file template.
Specifically, the object configuration information corresponding to each cluster may be preset, where the cluster refers to a cluster currently used for deploying an application. The determined file templates can be modified according to the configuration information of each object, so that a plurality of object configuration files are obtained. For example, a first object profile of a first cluster may be generated, and for example, a second object profile of a second cluster may be generated.
Further, the object configuration information may include information for performing differential configuration on different clusters, for example, a first configuration information is set for a first cluster, and a second configuration information is set for a second cluster, so that the platform may perform differential configuration on the clusters according to the configuration information.
In the embodiment, the user does not need to set object configuration files for each cluster one by one, so that the configuration efficiency of carrying out differential configuration on the clusters is improved.
In step 406, the object configuration file is sent to the cluster corresponding to the object configuration file, where the object configuration file is used to generate an object, and the object is used to manage the application deployed in the node of the cluster.
Specifically, the platform may distribute the object configuration file to the clusters, and specifically may send the object configuration file to the clusters corresponding to the object configuration file. For example, a first object profile is sent to a first cluster, a second object profile is sent to a second cluster, and a third object profile is sent to a third cluster.
Further, after the cluster receives the object configuration file, the cluster may generate an object according to the object configuration file, for example, generating a replyment according to replyment yaml.
After the objects are generated in the cluster, the application deployment process can be managed by using the objects, for example, when the App1 is deployed in a plurality of nodes of the first cluster after the object 1 is generated in the first cluster according to the first object configuration file of the App1, the flow of deploying the App1 in the cluster can be managed by the object 1.
In this way, different clusters can be configured differently for different clusters, so that different clusters can be configured differently. The configuration of a plurality of clusters for deploying the application can also be realized by configuring the object configuration file.
In an alternative embodiment, the object configuration information used to generate the object configuration file includes any one of the following information:
application release sequence, pause information after application release is completed.
The application release order refers to an order when an application is deployed in a node in a cluster, and the suspension information after the application release is completed refers to information whether suspension is required after the application is deployed in each node.
Because the object configuration information includes the application release order, pause information after the application release is completed, and the like, the object configuration file generated according to the object configuration information also includes the information, and the generated object also has corresponding information.
When the objects in the cluster manage the applications deployed in the nodes of the cluster, each application can be deployed according to the application release sequence and pause information after the application release is completed. For example, when three nodes in the first cluster are pod1, pod2 and pod3 respectively, and application app is deployed in the three nodes, management can be performed through objects, specifically, the application is deployed in pod2 first, then the application is deployed in pod1, then the application is deployed in pod3, and further, after each deployment is completed, the deployment can be paused for 30s, and then the next deployment is continued.
By the method, a richer deployment management mode can be provided, so that at least one node in the cluster can provide services to the outside, and the situation that the cluster cannot provide services to the outside when an application is deployed in the cluster is avoided.
Step 407, sending a service configuration file to each cluster recorded in the cluster list information, wherein the service configuration file is used for generating a service; the service is used to provide access addresses for the clusters.
The platform may also distribute the service configuration file to each cluster, and after the clusters receive the service configuration file, the clusters may generate service devices. The service is used to provide access addresses for clusters.
Service is a policy that can access logical groupings of nodes and can provide layer 4 load balancing capabilities. It may provide access addresses for clusters that are used for access between clusters.
After the system receives the traffic, the traffic can be distributed into the cluster, and specifically, the traffic can be sent into the cluster by using the access address of the cluster.
In this embodiment, the traffic may be forwarded to the cluster through a function provided by the service, so as to implement a traffic distribution function of the entire system.
Step 408, obtaining the application to be published, deploying the application in the nodes of each cluster recorded in the cluster list information, and determining the deployment flow according to the object of each preset cluster.
After the object and the service are configured in the cluster and the access controller independent of the cluster, the platform can acquire the application to be published, and deploy the application into the configured cluster, so as to realize the deployment of the application across the clusters.
Specifically, the cluster to which the application is deployed may be determined according to a preset cluster list corresponding to the application, and then the application to be deployed may be sent to the corresponding cluster, so that the cluster may deploy the application in an internal node.
During deployment, the clusters can perform personalized deployment on the application according to the preconfigured objects, and deployment flows of different clusters can be different.
Further, the deployed applications may include applications of a common version, and may also include applications of a test version. If the application of the normal version and the application of the test version are deployed at the same time, the applications share the portal controller, and the application of the normal version and the application of the test version deployed in the same cluster share the object, but different services may be used.
By the implementation mode, different configurations, deployment sequences and random pause points of the application in different clusters can be defined, and therefore the federal deployment requirement of the complex application is met.
Fig. 5 is a system configuration diagram of a multi-cluster deployed with applications, as shown in another exemplary embodiment of the present disclosure.
As shown in fig. 5, there are a plurality of clusters 51 in the system architecture, each cluster includes a plurality of nodes, and applications are deployed in the nodes, for example, app1 may be deployed and App2 may also be deployed.
The method provided according to the present disclosure may generate the ingress controller 52 according to the deployed application, for example, may generate the ingress controller 52 for forwarding the traffic of App1, and may also generate the ingress controller 53 for forwarding the traffic of App2.
Services and objects may also be configured in the cluster 51, respectively, for providing access addresses of the cluster, and objects for managing applications deployed in the cluster 51, such as for managing the services and objects of App1, and for managing the services and objects of App2.
Fig. 6 is a flow chart of a flow forwarding method in a multi-cluster scenario according to an exemplary embodiment of the present disclosure.
As shown in fig. 6, the traffic forwarding method in the multi-cluster scenario provided by the present disclosure includes:
In step 601, a flow is received and parsed.
A system provided with a plurality of clusters may receive traffic for accessing an application service, which may be a request for example, which the system may parse. For example, the intelligent DNS may be used to resolve a domain name of the flow, and send the resolved result to a preset ingress controller.
The inlet controller may be generated according to the embodiment shown in fig. 2 or fig. 4.
In step 602, if the traffic includes the test parameters, a first destination cluster provided with the test node and the test node deployed with the test version application are determined in the multiple clusters according to the preset ingress controller.
Step 603, forwarding the traffic to the test node of the first destination cluster.
In one embodiment, if the parsing result characterizes the flow including the test parameters, it indicates that the flow should be processed by the test version application.
Thus, the ingress controller may determine a destination cluster in which the test node is provided among the plurality of clusters, and determine the test node in the destination cluster. The test node refers to a test node deployed with a test version application.
Specifically, the ingress controller may determine an access address of the first destination cluster and an access address of the test node, and then the ingress controller may send traffic to the test node according to the two addresses.
Step 604, if the traffic does not include the test parameter, determining a destination cluster corresponding to the traffic and a destination node in the destination cluster according to a preset inlet controller; the destination node is deployed with a normal version application.
Step 605, the traffic is sent to the destination node.
In another embodiment, if the analysis result indicates that the flow does not include the test parameter, the flow is indicated to be processed by the normal version application.
Thus, the ingress controller may determine a second destination cluster corresponding to the traffic among the plurality of clusters and a destination node in the second destination cluster. The destination node refers to a node where a normal version application is deployed.
The ingress controller may determine a second destination cluster corresponding to the traffic and a destination node in the second destination cluster according to the traffic forwarding rule and the node deployed with the normal version application.
Specifically, the ingress controller may determine the access address of the second destination cluster and the access address of the destination node, and then the ingress controller may send the traffic to the destination node according to the two addresses.
Fig. 7 is a schematic structural diagram of a configuration apparatus of a multi-cluster deployed with an application according to an exemplary embodiment of the present disclosure.
As shown in fig. 7, the configuration apparatus 700 provided by the present disclosure for deploying multiple clusters of applications includes:
an obtaining unit 710, configured to obtain a configuration file and a preset cluster list corresponding to an application to be deployed; the configuration information is used for indicating a flow distribution rule, the cluster list comprises cluster information, and nodes in a cluster indicated by the cluster information are used for deploying the application;
a controller generating unit 720, configured to generate an entry controller according to the configuration file and cluster information included in the cluster table; the ingress controller is configured to receive traffic and forward the traffic to a destination node of a destination cluster corresponding to the traffic, where the destination cluster is any one of the clusters.
According to the configuration device for the multi-cluster deployed with the application, provided by the disclosure, through setting the inlet controller independent of the clusters, the flow can be controlled according to the unified rule, the flow can be forwarded in a unified way, and the requirement of a user on unified management of the access to the multi-cluster flow can be met.
Fig. 8 is a schematic structural diagram of a configuration apparatus of a multi-cluster deployed with an application according to another exemplary embodiment of the present disclosure.
As shown in fig. 8, in the configuration apparatus 800 provided with multiple clusters deployed with applications, the acquisition unit 810 is similar to the acquisition unit 710 described in fig. 7, and the controller generation unit 820 is similar to the controller generation unit 720 described in fig. 7.
In an alternative embodiment, the acquiring unit 810 is specifically configured to:
and obtaining a service configuration file and an inlet configuration file corresponding to the application to be distributed, wherein the inlet configuration file is a rule for distributing traffic to the cluster, and the service configuration file is a rule for forwarding traffic received by the cluster to nodes in the cluster.
In an alternative embodiment, the controller generating unit 820 includes:
a rule generating module 821, configured to determine a traffic forwarding rule according to a rule for distributing traffic to a cluster and a rule for forwarding traffic received by the cluster to nodes in the cluster;
and a controller generating module 822, configured to generate the ingress controller according to the traffic forwarding rule and the cluster information.
In an alternative embodiment, the obtaining unit 810 is further configured to: acquiring each object configuration file corresponding to each piece of cluster information included in the cluster list according to the cluster list and the application, wherein the object configuration files are files corresponding to both the clusters and the application;
The apparatus 800 further comprises an object file sending unit 830 configured to send the object configuration file to the cluster corresponding to the object configuration file, where the object configuration file is used to generate an object, and the object is used to manage the application deployed in a node of the cluster.
In an alternative embodiment, the acquiring unit 810 includes:
a history file obtaining module 811, configured to obtain a plurality of history object configuration files, where the history object configuration files are files corresponding to a plurality of clusters and the applications;
a template determining module 812, configured to determine a file template in the historical object configuration file according to the specified information;
the configuration file generating module 813 is configured to modify the file template according to each object configuration information corresponding to each cluster, so as to obtain each object configuration file corresponding to each preset cluster.
In an alternative embodiment, the object configuration information includes any one of the following information:
application release sequence, pause information after application release is completed.
In an alternative embodiment, the apparatus 800 further comprises:
a service file sending unit 840, configured to send the service configuration file to each cluster recorded in the cluster list information, where the service configuration file is used to generate a service; the service is used for providing access addresses of the clusters.
In an alternative embodiment, the apparatus 800 further includes an application deployment unit 840 for:
and acquiring the application to be published, deploying the application in the nodes of each cluster recorded in the cluster list information, and determining a deployment flow according to the object of each preset cluster.
Fig. 9 is a schematic structural diagram of a traffic forwarding device in a multi-cluster scenario according to an exemplary embodiment of the present disclosure.
As shown in fig. 9, a traffic forwarding device 900 in a multi-cluster scenario provided by the present disclosure includes:
a receiving unit 910, configured to receive a flow and parse the flow;
a forwarding unit 920, configured to determine, if the traffic includes the test parameter, a first destination cluster provided with the test node and a test node deployed with a test version application from the multiple clusters according to a preset ingress controller; the traffic is forwarded to the test node of the first destination cluster.
Wherein, the forwarding unit 920 is further configured to:
if the flow does not comprise the test parameters, determining a second target cluster corresponding to the flow and a target node in the second target cluster according to a preset inlet controller; the destination node is deployed with a common version application;
And sending the traffic to the destination node.
The present disclosure provides a configuration method, a traffic forwarding method, a device, a storage medium, and a program product, which are applied to an application deployment technology in a computer technology, so as to solve the problem that in the prior art, traffic cannot be controlled to access each cluster according to a unified rule.
In the technical scheme of the disclosure, the related processes of collecting, storing, using, processing, transmitting, providing, disclosing and the like of the personal information of the user accord with the regulations of related laws and regulations, and the public order colloquial is not violated.
According to embodiments of the present disclosure, the present disclosure also provides an electronic device, a readable storage medium and a computer program product.
According to an embodiment of the present disclosure, the present disclosure also provides a computer program product comprising: a computer program stored in a readable storage medium, from which at least one processor of an electronic device can read, the at least one processor executing the computer program causing the electronic device to perform the solution provided by any one of the embodiments described above.
Fig. 10 shows a schematic block diagram of an example electronic device 1000 that may be used to implement embodiments of the present disclosure. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular telephones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the disclosure described and/or claimed herein.
As shown in fig. 10, the apparatus 1000 includes a computing unit 1001 that can perform various appropriate actions and processes according to a computer program stored in a Read Only Memory (ROM) 1002 or a computer program loaded from a storage unit 1008 into a Random Access Memory (RAM) 1003. In the RAM 1003, various programs and data required for the operation of the device 1000 can also be stored. The computing unit 1001, the ROM 1002, and the RAM 1003 are connected to each other by a bus 1004. An input/output (I/O) interface 1005 is also connected to bus 1004.
Various components in device 1000 are connected to I/O interface 1005, including: an input unit 1006 such as a keyboard, a mouse, and the like; an output unit 1007 such as various types of displays, speakers, and the like; a storage unit 1008 such as a magnetic disk, an optical disk, or the like; and communication unit 1009 such as a network card, modem, wireless communication transceiver, etc. Communication unit 1009 allows device 1000 to exchange information/data with other devices via a computer network, such as the internet, and/or various telecommunications networks.
The computing unit 1001 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of computing unit 1001 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various computing units running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 1001 performs the respective methods and processes described above, for example, a configuration method of a multi-cluster in which an application is deployed or a traffic forwarding method in a multi-cluster scenario. For example, in some embodiments, a method of configuration of a multi-cluster or a method of traffic forwarding in a multi-cluster scenario where an application is deployed may be implemented as a computer software program tangibly embodied on a machine-readable medium, such as storage unit 1008. In some embodiments, part or all of the computer program may be loaded and/or installed onto device 1000 via ROM 1002 and/or communication unit 1009. When the computer program is loaded into RAM 1003 and executed by the computing unit 1001, one or more steps of the above-described configuration method of multiple clusters deployed with applications or the traffic forwarding method in a multiple cluster scenario may be performed. Alternatively, in other embodiments, the computing unit 1001 may be configured by any other suitable way (e.g., by means of firmware) to perform a multi-cluster configuration method in which applications are deployed or a traffic forwarding method in a multi-cluster scenario.
Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuit systems, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), systems On Chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs, the one or more computer programs may be executed and/or interpreted on a programmable system including at least one programmable processor, which may be a special purpose or general-purpose programmable processor, that may receive data and instructions from, and transmit data and instructions to, a storage system, at least one input device, and at least one output device.
Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program code may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus such that the program code, when executed by the processor or controller, causes the functions/operations specified in the flowchart and/or block diagram to be implemented. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, 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), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and pointing device (e.g., a mouse or trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic input, speech input, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a background component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such background, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), and the internet.
The computer system may include a client and a server. The client and server are typically remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also called a cloud computing server or a cloud host, and is a host product in a cloud computing service system, so that the defects of high management difficulty and weak service expansibility in the traditional physical hosts and VPS service ("Virtual Private Server" or simply "VPS") are overcome. The server may also be a server of a distributed system or a server that incorporates a blockchain.
It should be appreciated that various forms of the flows shown above may be used to reorder, add, or delete steps. For example, the steps recited in the present disclosure may be performed in parallel or sequentially or in a different order, provided that the desired results of the technical solutions of the present disclosure are achieved, and are not limited herein.
The above detailed description should not be taken as limiting the scope of the present disclosure. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives are possible, depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present disclosure are intended to be included within the scope of the present disclosure.
Claims (18)
1. A method of configuring a multi-cluster with applications deployed, comprising:
acquiring a service configuration file, an inlet configuration file and a preset cluster list corresponding to an application to be distributed; the service configuration file is a rule for forwarding traffic received by the cluster to nodes in the cluster, the cluster list comprises cluster information, and the nodes in the cluster indicated by the cluster information are used for deploying the application;
Determining a traffic forwarding rule according to a rule for distributing traffic to the cluster and a rule for forwarding traffic received by the cluster to nodes in the cluster;
generating an inlet controller according to the flow forwarding rule and the cluster information; the ingress controller is configured to receive traffic and forward the traffic to a destination node of a destination cluster corresponding to the traffic, where the destination cluster is any one of the clusters.
2. The method of claim 1, the method further comprising:
acquiring each object configuration file corresponding to each piece of cluster information included in the cluster list according to the cluster list and the application, wherein the object configuration files are files corresponding to both the clusters and the application;
and sending the object configuration file to the cluster corresponding to the object configuration file, wherein the object configuration file is used for generating an object, and the object is used for managing the application deployed in the node of the cluster.
3. The method of claim 2, wherein the obtaining each object profile corresponding to each cluster information included in the cluster list comprises:
Acquiring a plurality of historical object configuration files, wherein the historical object configuration files correspond to a plurality of clusters and the application;
determining a file template in the history object configuration file according to the specified information;
and modifying the file template according to the object configuration information corresponding to each cluster to obtain each object configuration file corresponding to each preset cluster.
4. A method according to claim 3, wherein the object configuration information comprises any one of the following:
application release sequence, pause information after application release is completed.
5. The method of claim 1, further comprising:
sending the service configuration file to each cluster recorded in the cluster list information, wherein the service configuration file is used for generating a service; the service is used for providing access addresses of the clusters.
6. The method of claim 3 or 4, further comprising:
and acquiring the application to be published, deploying the application in the nodes of each cluster recorded in the cluster list information, and determining a deployment flow according to the object of each preset cluster.
7. A traffic forwarding method under a multi-cluster scene comprises the following steps:
Receiving a flow, and analyzing the flow;
if the flow comprises the test parameters, determining a first target cluster provided with the test node and the test node deployed with the test version application in a plurality of clusters according to a preset inlet controller;
forwarding the traffic to a test node of the first destination cluster;
the inlet controller is generated by:
acquiring a service configuration file, an inlet configuration file and a preset cluster list corresponding to an application to be distributed;
the service configuration file is a rule for forwarding traffic received by the cluster to nodes in the cluster, the cluster list comprises cluster information, and the nodes in the cluster indicated by the cluster information are used for deploying the application;
determining a traffic forwarding rule according to a rule for distributing traffic to the cluster and a rule for forwarding traffic received by the cluster to nodes in the cluster;
generating the inlet controller according to the flow forwarding rule and the cluster information; the ingress controller is configured to receive traffic and forward the traffic to a destination node of a destination cluster corresponding to the traffic, where the destination cluster is any one of the clusters.
8. The method of claim 7, wherein if the traffic does not include a test parameter, determining a second destination cluster corresponding to the traffic and a destination node in the second destination cluster according to a preset ingress controller; the destination node is deployed with a common version application;
and sending the traffic to the destination node.
9. A multi-cluster configuration apparatus deployed with applications, comprising:
the acquisition unit is used for acquiring a service configuration file, an inlet configuration file and a preset cluster list, wherein the service configuration file and the inlet configuration file correspond to the application to be distributed; the service configuration file is a rule for forwarding traffic received by the cluster to nodes in the cluster, the cluster list comprises cluster information, and the nodes in the cluster indicated by the cluster information are used for deploying the application;
a controller generating unit for determining a traffic forwarding rule according to a rule for distributing traffic to the cluster and a rule for forwarding traffic received by the cluster to nodes in the cluster; generating an inlet controller according to the flow forwarding rule and the cluster information; the ingress controller is configured to receive traffic and forward the traffic to a destination node of a destination cluster corresponding to the traffic, where the destination cluster is any one of the clusters.
10. The apparatus of claim 9, wherein:
the acquisition unit is further configured to: acquiring each object configuration file corresponding to each piece of cluster information included in the cluster list according to the cluster list and the application, wherein the object configuration files are files corresponding to both the clusters and the application;
the device further comprises an object file sending unit, configured to send the object configuration file to the cluster corresponding to the object configuration file, where the object configuration file is used to generate an object, and the object is used to manage the application deployed in a node of the cluster.
11. The apparatus of claim 10, wherein the acquisition unit comprises:
a history file obtaining module, configured to obtain a plurality of history object configuration files, where the history object configuration files correspond to a plurality of clusters and the application;
the template determining module is used for determining a file template in the history object configuration file according to the specified information;
and the configuration file generation module is used for modifying the file template according to the object configuration information corresponding to each cluster to obtain each object configuration file corresponding to each preset cluster.
12. The apparatus of claim 11, wherein the object configuration information comprises any of the following:
application release sequence, pause information after application release is completed.
13. The apparatus of claim 9, further comprising:
a service file sending unit, configured to send the service configuration file to each cluster recorded in the cluster list information, where the service configuration file is used to generate a service; the service is used for providing access addresses of the clusters.
14. The apparatus according to claim 11 or 12, further comprising an application deployment unit for:
and acquiring the application to be published, deploying the application in the nodes of each cluster recorded in the cluster list information, and determining a deployment flow according to the object of each preset cluster.
15. A traffic forwarding device in a multi-cluster scenario, comprising:
the receiving unit is used for receiving the flow and analyzing the flow;
the forwarding unit is used for determining a first target cluster provided with a test node and a test node deployed with a test version application in a plurality of clusters according to a preset inlet controller if the flow comprises the test parameters; forwarding the traffic to a test node of the first destination cluster;
The inlet controller is generated by:
acquiring a service configuration file, an inlet configuration file and a preset cluster list corresponding to an application to be distributed;
the service configuration file is a rule for forwarding traffic received by the cluster to nodes in the cluster, the cluster list comprises cluster information, and the nodes in the cluster indicated by the cluster information are used for deploying the application;
determining a traffic forwarding rule according to a rule for distributing traffic to the cluster and a rule for forwarding traffic received by the cluster to nodes in the cluster; generating the inlet controller according to the flow forwarding rule and the cluster information; the ingress controller is configured to receive traffic and forward the traffic to a destination node of a destination cluster corresponding to the traffic, where the destination cluster is any one of the clusters.
16. The apparatus of claim 15, wherein the forwarding unit is further configured to:
if the flow does not comprise the test parameters, determining a second target cluster corresponding to the flow and a target node in the second target cluster according to a preset inlet controller; the destination node is deployed with a common version application;
And sending the traffic to the destination node.
17. An electronic device, comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-8.
18. A non-transitory computer readable storage medium storing computer instructions for causing the computer to perform the method of any one of claims 1-8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111327832.0A CN114070889B (en) | 2021-11-10 | 2021-11-10 | Configuration method, traffic forwarding device, storage medium, and program product |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111327832.0A CN114070889B (en) | 2021-11-10 | 2021-11-10 | Configuration method, traffic forwarding device, storage medium, and program product |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114070889A CN114070889A (en) | 2022-02-18 |
| CN114070889B true CN114070889B (en) | 2023-11-14 |
Family
ID=80274753
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111327832.0A Active CN114070889B (en) | 2021-11-10 | 2021-11-10 | Configuration method, traffic forwarding device, storage medium, and program product |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114070889B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115086321B (en) * | 2022-06-14 | 2024-04-05 | 京东科技信息技术有限公司 | Multi-cluster traffic forwarding method and device and electronic equipment |
Citations (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106407011A (en) * | 2016-09-20 | 2017-02-15 | 焦点科技股份有限公司 | A routing table-based search system cluster service management method and system |
| WO2017113929A1 (en) * | 2015-12-29 | 2017-07-06 | 中兴通讯股份有限公司 | Method and controller for controlling forwarding device cluster in software-defined networking |
| CN108156079A (en) * | 2017-12-29 | 2018-06-12 | 深信服网络科技（深圳）有限公司 | A kind of data packet forwarding system and method based on cloud service platform |
| CN109656782A (en) * | 2018-12-24 | 2019-04-19 | 成都四方伟业软件股份有限公司 | Visual scheduling monitoring method, device and server |
| CN110572436A (en) * | 2019-08-12 | 2019-12-13 | 浙江讯盟科技有限公司 | Multi-place cross-cluster server deployment method and system |
| CN111181801A (en) * | 2019-12-04 | 2020-05-19 | 腾讯云计算（北京）有限责任公司 | Node cluster testing method and device, electronic equipment and storage medium |
| CN111367662A (en) * | 2020-02-26 | 2020-07-03 | 普信恒业科技发展（北京）有限公司 | Load balancing method, device and system |
| CN112653632A (en) * | 2019-10-09 | 2021-04-13 | 北京京东振世信息技术有限公司 | Flow control realization method and device |
| CN112910959A (en) * | 2021-01-15 | 2021-06-04 | 北京开物数智科技有限公司 | SDN-based network interconnection method for multiple Kubernets clusters |
| CN113055220A (en) * | 2019-12-26 | 2021-06-29 | 瞻博网络公司 | Scalable and robust network management for cloud-based NAT environments |
| CN113138776A (en) * | 2021-03-25 | 2021-07-20 | 杭州博联智能科技股份有限公司 | Template-based cluster automatic deployment method, device, equipment and medium |
| CN113220451A (en) * | 2021-04-30 | 2021-08-06 | 江苏云从曦和人工智能有限公司 | Method, system, device and storage medium for deploying distributed cluster system |
| CN113259272A (en) * | 2021-05-13 | 2021-08-13 | 中国建设银行股份有限公司 | Flow management method, device and equipment based on virtual gateway |
| CN113485821A (en) * | 2021-09-08 | 2021-10-08 | 北京交通大学 | High-reliability video conference system, control method thereof and storage medium |
| CN113626286A (en) * | 2021-08-04 | 2021-11-09 | 北京汇钧科技有限公司 | Multi-cluster instance processing method and device, electronic equipment and storage medium |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11159607B2 (en) * | 2020-03-03 | 2021-10-26 | International Business Machines Corporation | Management for a load balancer cluster |
-
2021
- 2021-11-10 CN CN202111327832.0A patent/CN114070889B/en active Active
Patent Citations (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017113929A1 (en) * | 2015-12-29 | 2017-07-06 | 中兴通讯股份有限公司 | Method and controller for controlling forwarding device cluster in software-defined networking |
| CN106407011A (en) * | 2016-09-20 | 2017-02-15 | 焦点科技股份有限公司 | A routing table-based search system cluster service management method and system |
| CN108156079A (en) * | 2017-12-29 | 2018-06-12 | 深信服网络科技（深圳）有限公司 | A kind of data packet forwarding system and method based on cloud service platform |
| CN109656782A (en) * | 2018-12-24 | 2019-04-19 | 成都四方伟业软件股份有限公司 | Visual scheduling monitoring method, device and server |
| CN110572436A (en) * | 2019-08-12 | 2019-12-13 | 浙江讯盟科技有限公司 | Multi-place cross-cluster server deployment method and system |
| CN112653632A (en) * | 2019-10-09 | 2021-04-13 | 北京京东振世信息技术有限公司 | Flow control realization method and device |
| CN111181801A (en) * | 2019-12-04 | 2020-05-19 | 腾讯云计算（北京）有限责任公司 | Node cluster testing method and device, electronic equipment and storage medium |
| CN113055220A (en) * | 2019-12-26 | 2021-06-29 | 瞻博网络公司 | Scalable and robust network management for cloud-based NAT environments |
| CN111367662A (en) * | 2020-02-26 | 2020-07-03 | 普信恒业科技发展（北京）有限公司 | Load balancing method, device and system |
| CN112910959A (en) * | 2021-01-15 | 2021-06-04 | 北京开物数智科技有限公司 | SDN-based network interconnection method for multiple Kubernets clusters |
| CN113138776A (en) * | 2021-03-25 | 2021-07-20 | 杭州博联智能科技股份有限公司 | Template-based cluster automatic deployment method, device, equipment and medium |
| CN113220451A (en) * | 2021-04-30 | 2021-08-06 | 江苏云从曦和人工智能有限公司 | Method, system, device and storage medium for deploying distributed cluster system |
| CN113259272A (en) * | 2021-05-13 | 2021-08-13 | 中国建设银行股份有限公司 | Flow management method, device and equipment based on virtual gateway |
| CN113626286A (en) * | 2021-08-04 | 2021-11-09 | 北京汇钧科技有限公司 | Multi-cluster instance processing method and device, electronic equipment and storage medium |
| CN113485821A (en) * | 2021-09-08 | 2021-10-08 | 北京交通大学 | High-reliability video conference system, control method thereof and storage medium |
Non-Patent Citations (2)
| Title |
|---|
| Kubernetes高可用集群的部署实践;盛乐标;周庆林;游伟倩;张予倩;;电脑知识与技术(26);全文 * |
| 云环境下基于Kubernetes集群系统的容器网络研究与优化;刘渊;乔巍;;信息网络安全(03);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114070889A (en) | 2022-02-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108696581B (en) | Distributed information caching method and device, computer equipment and storage medium | |
| CN113742031B (en) | Node state information acquisition method and device, electronic equipment and readable storage medium | |
| CN107800565B (en) | Inspection method, inspection device, inspection system, computer equipment and storage medium | |
| CN107729176B (en) | Disaster recovery method and disaster recovery system for configuration file management system | |
| CN114650223B (en) | Network configuration method and device of Kubernetes cluster and electronic equipment | |
| CN109828830B (en) | Method and apparatus for managing containers | |
| CN114389969B (en) | Method and device for testing client, electronic equipment and storage medium | |
| CN114070889B (en) | Configuration method, traffic forwarding device, storage medium, and program product | |
| CN113612643B (en) | Network configuration method, device and equipment of cloud mobile phone and storage medium | |
| CN113641388A (en) | Cloud mobile phone updating method, related device and computer program product | |
| CN112988738B (en) | Data slicing method and device for block chain | |
| CN111767126A (en) | System and method for distributed batch processing | |
| CN113541987A (en) | Method and device for updating configuration data | |
| CN114443057B (en) | Deployment of conversation model, conversation method, device, electronic equipment and storage medium | |
| CN113360689B (en) | Image retrieval system, method, related device and computer program product | |
| CN116319758A (en) | Data migration method, device, electronic equipment and readable storage medium | |
| CN115442129A (en) | Method, device and system for managing cluster access authority | |
| CN115113911A (en) | Software management system and method | |
| CN113468053A (en) | Application system testing method and device | |
| CN113760446A (en) | Resource scheduling method, device, equipment and medium | |
| CN115277568B (en) | Data transmission method, device, equipment and storage medium | |
| CN115981847B (en) | Service grid deployment method and device, electronic equipment and storage medium | |
| US20230325267A1 (en) | Selective privileged container augmentation | |
| CN116382852A (en) | Micro-service deployment method and device, electronic equipment and medium | |
| CN117997740A (en) | Container configuration information updating method and device, electronic equipment and computer storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |