CN114070889A - Configuration method, traffic forwarding method, device, storage medium, and program product - Google Patents
Configuration method, traffic forwarding method, device, storage medium, and program product Download PDFInfo
- Publication number
- CN114070889A CN114070889A CN202111327832.0A CN202111327832A CN114070889A CN 114070889 A CN114070889 A CN 114070889A CN 202111327832 A CN202111327832 A CN 202111327832A CN 114070889 A CN114070889 A CN 114070889A
- Authority
- CN
- China
- Prior art keywords
- cluster
- application
- traffic
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims description 72
- 238000012360 testing method Methods 0.000 claims description 48
- 238000004590 computer program Methods 0.000 claims description 17
- 238000012545 processing Methods 0.000 claims description 14
- 230000008569 process Effects 0.000 claims description 9
- 239000000126 substance Substances 0.000 claims description 2
- 238000010586 diagram Methods 0.000 description 15
- 101100264195 Caenorhabditis elegans app-1 gene Proteins 0.000 description 12
- 238000004891 communication Methods 0.000 description 8
- 238000005516 engineering process Methods 0.000 description 7
- 230000006870 function Effects 0.000 description 5
- 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
- 238000004458 analytical method Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 101150109289 tcf21 gene Proteins 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 238000013473 artificial intelligence Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 230000001413 cellular effect Effects 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
- 230000006872 improvement Effects 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
- -1 pod2 Proteins 0.000 description 1
- 238000011084 recovery Methods 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
- 239000000725 suspension Substances 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The scheme includes 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 application; generating an entrance controller according to the configuration file and cluster information included in the cluster list; 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. In the embodiment, the inlet controller independent of the cluster is arranged, so that the flow can be controlled according to a uniform rule, the flow can be uniformly forwarded, and the requirement of a user on uniform management of the flow accessing multiple clusters can be met.
Description
Technical Field
The present disclosure relates to application deployment technologies in computer technologies, 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, the container technology standardized by kubernets has become a cloud computing fact standard.
In a service form and a cloud disaster backup scene, multi-region deployment needs to be performed on services, for example, one same service is deployed in a plurality of clusters, and when a service of one cluster is down, traffic can be rapidly migrated to other clusters, so that the availability of the service is ensured.
In the prior art, there are multiple schemes for managing kubernets application deployment under multiple clusters, and these schemes do not support the rule of accessing traffic across multiple clusters when managing kubernets application deployment under multiple clusters, so that traffic cannot be controlled to access each cluster according to a uniform rule.
Disclosure of Invention
The present disclosure provides a configuration method, a traffic forwarding method, a device, a storage medium, and a program product, which solve the problem in the prior art that traffic cannot be controlled to access each cluster according to a uniform rule.
According to a first aspect of the present disclosure, there is provided a configuration method of multiple 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 entrance controller according to the configuration file and cluster information included in the cluster list; 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, a traffic forwarding method in a multi-cluster scenario is provided, including:
receiving flow and analyzing the flow;
if the flow comprises the test parameters, determining a first target cluster provided with test nodes and the test nodes deployed with test version applications in the plurality of clusters according to a preset entrance 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 multiple clusters deployed with an application, including:
the device comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for 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;
the controller generating unit is used for generating an entrance controller according to the configuration file and the cluster information included in the cluster list; 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 apparatus 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 deploying the test node with a test version application in the plurality of clusters according to a preset entrance 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 content of the first and second substances,
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 having stored thereon 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 computer program, execution of the computer program by the at least one processor causing the electronic device to perform the method of the first or second aspect.
The configuration method, the flow forwarding method, the 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 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 application; generating an entrance controller according to the configuration file and cluster information included in the cluster list; 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. In the embodiment, the inlet controller independent of the cluster is arranged, so that the flow can be controlled according to a uniform rule, the flow can be uniformly forwarded, and the requirement of a user on uniform management of the flow accessing multiple clusters can be met.
It should be understood that the statements in this section do not necessarily identify key or critical features of the embodiments of the present disclosure, nor do they limit the scope of the present disclosure. Other features of the present disclosure will become apparent from the following description.
Drawings
The drawings are included to provide a better understanding of the present solution and are not to be construed as limiting the present disclosure. Wherein:
FIG. 1 is a system block diagram illustrating multiple clusters deployed with an application in accordance with an exemplary embodiment;
FIG. 2 is a flowchart illustrating a configuration method for multiple clusters deployed with an application according to an exemplary embodiment of the present disclosure;
FIG. 3 is a system block diagram illustrating multiple clusters deployed with an application in accordance with an exemplary embodiment of the present disclosure;
FIG. 4 is a flowchart illustrating a configuration method of multiple clusters deployed with an application according to another exemplary embodiment of the present disclosure;
FIG. 5 is a system block diagram of a multiple cluster deployed with an application according to another exemplary embodiment of the present disclosure;
fig. 6 is a flowchart illustrating a flow of a traffic forwarding method in a multi-cluster scenario according to an exemplary embodiment of the present disclosure;
FIG. 7 is a block diagram illustrating a configuration apparatus of a multi-cluster with applications deployed therein according to an exemplary embodiment of the present disclosure;
FIG. 8 is a schematic structural diagram of a configuration device with multiple clusters deployed with an application according to another exemplary embodiment of the present disclosure;
fig. 9 is a schematic structural diagram of a traffic forwarding apparatus in a multi-cluster scenario according to an exemplary embodiment of the present disclosure;
FIG. 10 is a block diagram of an electronic device used to implement methods of embodiments of the present disclosure.
Detailed Description
Exemplary embodiments of the present disclosure are described below with reference to the accompanying drawings, in which various details of the embodiments of the disclosure are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those 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 block diagram illustrating a multi-cluster deployed application in an exemplary embodiment.
As shown in fig. 1, a plurality of clusters 11 may be set up for business needs or disaster recovery backup needs, and an application may be deployed in each cluster 11. If the application deployment adopts a container technology, a container is set in the cluster, and the application is containerized.
In the system architecture, after receiving the traffic for accessing the application, the system randomly forwards the traffic to one of the clusters 11 through the intelligent DNS. An Ingress Controller (Ingress Controller) is provided in each cluster 11, and after traffic enters the cluster 11, the Ingress Controller in the cluster 11 forwards the traffic to a node (Pod) in the cluster 11.
However, this method cannot set traffic rules across multiple clusters, and cannot control traffic access to each cluster according to a uniform rule.
In order to solve the technical problem, in the scheme provided by the present disclosure, an ingress controller independent from each cluster is provided, and the ingress controller can determine which cluster the traffic is forwarded to and which node of the cluster the traffic needs to be forwarded to based on a preset traffic distribution rule, so that the accessed traffic can be forwarded in a unified manner, and a user can perform unified management on the traffic accessing multiple clusters with applications.
Fig. 2 is a flowchart illustrating a configuration method of multiple clusters deployed with an application according to an exemplary embodiment of the present disclosure.
As shown in fig. 2, the method for configuring multiple clusters deployed with an application provided by the present disclosure includes:
step 201, 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 the cluster indicated by the cluster information are used for deploying 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 can also 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 specifically, the applications may be deployed in each node in the cluster. When a corresponding application program is set in the terminal device, the terminal device may use a function provided by the application service, and specifically may distribute a request sent by the terminal device to a node of the cluster, and then the node processes the request according to the deployed application, and feeds back a processing result to the terminal device.
In particular, when an application is deployed in multiple clusters, the clusters may be configured.
Further, when configuring the multiple clusters, a configuration file of the application to be published may be obtained, and the configuration information is used to indicate a traffic distribution rule. For example, forwarding is performed randomly, and then, for example, forwarding traffic according to the load condition of the cluster, and for example, forwarding traffic according to the gray scale test information.
In practical application, the configuration file may be set by a user according to requirements, and may include, for example, 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 configuring the multiple clusters, a preset cluster list corresponding to the application to be issued can be obtained. The cluster list includes cluster information, and the nodes in the cluster 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 a requirement, where the cluster list records a plurality of cluster information, such as a cluster identifier. For example, if the cluster list includes the identifier of the first cluster, the identifier of the second cluster, and the identifier of the third cluster, the representation needs to deploy the application to be published to the three clusters, and therefore, the three clusters need to be configured.
Step 202, generating an entrance controller according to the configuration file and cluster information included in the cluster list; 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.
Further, an entry controller may be generated in the platform. After the application to be published 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 actual application, the ingress controller may be generated according to the configuration file and the cluster information included in the cluster list. For example, a traffic distribution rule may be determined according to information in the configuration file, information of a cluster and a node that can receive traffic may be determined according to the cluster information, and an entry controller may be 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, forward the received traffic to any node in the cluster where the application is deployed.
Fig. 3 is a system block diagram of a multi-cluster deployed with an application according to an exemplary embodiment of the present disclosure.
As shown in fig. 3, there are multiple clusters 31 in the system architecture, each cluster includes multiple nodes, and applications are deployed in the nodes, such as App1 and App 2.
Methods provided in accordance with the present disclosure may generate an ingress controller from a deployed application.
In one embodiment, an ingress controller for forwarding the traffic of App1 may be generated, and an ingress controller for forwarding the traffic of App2 may also be generated. After receiving the traffic of App1, the system may forward the traffic to the ingress controller 32 by using the intelligent DNS, and forward the traffic to the node of the cluster by using the ingress controller corresponding to App1, and after receiving the traffic of App2, the system may forward the traffic to the ingress controller corresponding to App2 by using the intelligent DNS, and forward the traffic to the node of the cluster by using the ingress controller corresponding to App 2.
In another embodiment, only one ingress controller may be generated, and the traffic forwarding rule of each App is written into the ingress controller, so that the ingress controller may forward the traffic according to the traffic forwarding rule of each App.
The configuration method of the multiple clusters with the applications comprises the steps of obtaining a configuration file corresponding to the applications 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 application; generating an entrance controller according to the configuration file and cluster information included in the cluster list; 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. In the embodiment, the inlet controller independent of the cluster is arranged, so that the flow can be controlled according to a uniform rule, the flow can be uniformly forwarded, and the requirement of a user on uniform management of the flow accessing multiple clusters can be met.
Fig. 4 is a flowchart illustrating a configuration method of multiple clusters deployed with an application according to another exemplary embodiment of the present disclosure.
As shown in fig. 4, the method for configuring multiple clusters deployed with an application provided by the present disclosure includes:
Step 401 is similar to the manner of obtaining the cluster list in step 201, and is not described again.
When the cluster is configured, a service configuration file and an entry configuration file corresponding to the application to be issued can be obtained. The service configuration file and the entry configuration file corresponding to the application to be issued can be set in advance according to requirements.
Specifically, the service profile may be, for example, service yaml, where a rule for forwarding traffic received by the cluster to a node in the cluster is recorded, and a user may set the service profile according to a requirement.
Further, the ingress profile may be, for example, ingress yaml, in which a rule for forwarding the received traffic to any one of the plurality of clusters is recorded, and the user may set the ingress profile according to a requirement.
In this embodiment, the user may set traffic distribution rules according to the demand, and then may generate an ingress controller according to the rules, and the ingress controller may forward the traffic according to the rules, so that the traffic may be forwarded according to the unified rules.
The platform may obtain an overall traffic forwarding rule by combining a rule for distributing traffic to a cluster and a rule for forwarding traffic received by the cluster to a node in the cluster.
For example, the rule for distribution of traffic to the clusters includes forwarding the traffic into the first cluster when the first condition is satisfied. And forwarding the traffic received by the cluster to the first node in the cluster when the rule for forwarding the traffic received by the cluster to the nodes in the cluster includes that the second condition is met. Based on this, a traffic forwarding rule may be generated to forward the traffic to the first node of the first cluster when the traffic satisfies the first condition and the second condition.
Specifically, after determining the overall traffic forwarding rule, the platform may generate the ingress controller according to the information of the cluster that needs to be deployed.
Further, the ingress controller may record an applied traffic forwarding rule and may also record cluster information corresponding to the application, and then, after receiving the applied traffic, 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 further can perform uniform forwarding processing on the traffic of the application through the ingress controller.
In actual application, the platform may further obtain an object configuration file of the application to be published, and specifically, may obtain each object configuration file corresponding to a 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 correspond to the first cluster, the second cluster, and the third cluster, respectively.
The object configuration file may be set in advance for a cluster for deploying the application to be published. The object configuration file may be, for example, deployment xml, and the object configuration file is used to instruct the cluster to generate an object, so as to manage the applications deployed in the cluster through the object.
Specifically, when the object configuration file is obtained, the file template may be obtained first, and then the object configuration file is obtained by adjusting based on the file template.
Furthermore, a plurality of historical object configuration files can be obtained, wherein the historical object configuration files correspond to a plurality of clusters and applications; determining a file template in the historical 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 files corresponding to each preset cluster.
In actual application, if the application to be released is an upgraded version of an existing application, corresponding historical object configuration files are provided when each version of the existing application is upgraded. For example, there is App1, which is released in a first version when it is released for the first time, needs to set one history object profile v1 when it is released for App1 of that version, is released in a second version when it is released for the second time, and needs to set one history object profile v2 when it is released for App.
Accordingly, a plurality of historical object profiles corresponding to the applications to be published may be obtained, which may be files corresponding to the cluster in which the App is deployed. Such as a historical object profile used when deployed in a first cluster, or a historical object profile used when deployed in a second cluster.
Wherein, the specific information used for determining the file template in the history object configuration file can be preset. For example, the user may preset a version identifier for indicating which historical object configuration file is determined as the file template.
Specifically, the object configuration information corresponding to each cluster may be preset, where the cluster is a cluster currently used for deploying the application. The determined file template can be modified according to the configuration information of each object, and then a plurality of object configuration files are obtained. For example, a first object profile may be generated for a first cluster, and for example, a second object profile may be generated for a second cluster.
Further, the object configuration information may include information for performing differential configuration on different clusters, for example, setting first configuration information for a first cluster and setting second configuration information 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 the object configuration files for each cluster one by one, so that the configuration efficiency of performing differential configuration on the clusters is improved.
Specifically, the platform may distribute the object configuration file to the cluster, and specifically, may send the object configuration file to the cluster 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 receiving the object configuration file, the cluster may generate an object according to the object configuration file, for example, generate a deployment from deployment yaml.
After the objects are generated in the cluster, the objects can be used to manage the application deployment process, for example, after an object 1 is generated in the first cluster according to the first object configuration file of App1, when App1 is deployed in a plurality of nodes of the first cluster, the process of deploying App1 in the cluster can be managed through the object 1.
By the method, different cluster differentiated configuration objects can be provided, so that different clusters are configured in a differentiated manner. And the configuration of a plurality of clusters for deploying the application can be realized in a mode of configuring the object configuration file.
In an optional implementation manner, the object configuration information used for generating the object configuration file includes any one of the following information:
application release sequence, and pause information after application release is completed.
The application issuing sequence refers to a sequence when the applications are deployed in the nodes in the cluster, and the pause information after the application issuing is completed refers to information on whether the applications need to be paused after the applications are deployed in each node.
Since the object configuration information includes the application distribution sequence, the pause information after the application distribution is completed, and the like, the object configuration file generated according to the object configuration information also includes these information, and the generated object also has corresponding information.
When the object in the cluster manages the applications deployed in the nodes of the cluster, each application can be deployed according to the application publishing sequence and the suspension information after the application publishing is completed. For example, there are three nodes in the first cluster, which are pod1, pod2, and pod3, respectively, when the application apps are deployed in the three nodes, management may be performed through an object, specifically, the application is deployed in pod2, the application is deployed in pod1, the application is deployed in pod3, or after each deployment is completed, the deployment may be suspended for 30 seconds, and then the next deployment may be continued.
By the method, richer deployment management modes can be provided, so that at least one node in the cluster can provide services to the outside, and the cluster cannot provide services to the outside when the application is deployed in the cluster.
The platform can also distribute the service configuration file to each cluster, and the clusters can generate service services after receiving the service configuration file. The service is used to provide an access address for the cluster.
Service is a policy that can access logical groupings of nodes and can provide a 4-layer load balancing capability. It may provide access addresses for the clusters, which are used for access between the clusters.
After receiving the traffic, the system may allocate the traffic to the cluster, and specifically, may send the traffic to the cluster by using the access address of the cluster.
In this embodiment, the traffic may be forwarded to the cluster through the function provided by the service, so as to implement the traffic distribution function of the entire system.
After the object and the service are configured in the cluster and the access controller independent of the cluster is configured, the platform can acquire the application to be released and deploy the application to the configured cluster, so that cross-cluster application deployment is realized.
Specifically, the cluster deployed by the application may be determined according to a preset cluster list corresponding to the application, and the application to be published 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 applications according to the pre-configured objects, and the deployment traffic of different clusters can be different.
Further, the deployed application may include a normal version of the application, and may also include a test version of the application. If the common version application and the test version application are deployed simultaneously, the applications share the portal controller, and the common version application and the test version application deployed in the same cluster share the object, but different services can be used.
By the implementation mode, differential configuration and deployment sequence of the application in different cluster deployment can be defined, and the pause point is set at will in the deployment process, so that the requirement of complex application federal deployment is met.
Fig. 5 is a system block diagram of a multi-cluster deployed with an application according to another exemplary embodiment of the present disclosure.
As shown in fig. 5, a plurality of clusters 51 exist in the system architecture, each cluster includes a plurality of nodes, and an application is deployed in a node, for example, App1 may be deployed, and App2 may also be deployed.
The method provided by the present disclosure may generate ingress controller 52 according to the deployed application, for example, may generate ingress controller 52 for forwarding App1 traffic, and may also generate ingress controller 53 for forwarding App2 traffic.
Services and objects may also be configured in the cluster 51, respectively, the services for providing access addresses of the cluster, the objects for managing applications deployed in the cluster 51, such as services and objects for managing App1, and services and objects for managing App 2.
Fig. 6 is a flowchart illustrating a traffic 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 a multi-cluster scenario provided by the present disclosure includes:
A system provided with a plurality of clusters may receive traffic for accessing an application service, which may be, for example, a request, and the system may parse the traffic. For example, the domain name of the traffic may be resolved by using an intelligent DNS, and the resolution result may be sent to a preset ingress controller.
The access controller may be generated according to the embodiments shown in fig. 2 or fig. 4.
Step 602, if the traffic includes the test parameter, determining a first destination cluster provided with the test node and the test node deployed with the test version application in the plurality of clusters according to a preset ingress controller.
In one embodiment, if the analysis result indicates that the traffic includes the test parameter, it indicates that the traffic should be processed by the test version application.
Thus, the ingress controller may determine a destination cluster in which the test node is disposed among the plurality of clusters and determine the test node in the destination cluster. The test node is a test node with a test version application deployed.
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 the traffic to the test node according to the two addresses.
In another embodiment, if the analysis result indicates that the traffic does not include the test parameter, it indicates that the traffic should be processed by the application of the normal version.
Thus, the ingress controller may determine, among the plurality of clusters, a second destination cluster corresponding to the traffic and a destination node in the second destination cluster. The destination node refers to a node deployed with a common version application.
The ingress controller may determine, according to the traffic forwarding rule and the node deployed with the common version application, a second destination cluster corresponding to the traffic and a destination node in the second destination cluster.
Specifically, the ingress controller may determine an access address of the second destination cluster and an 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 multiple clusters deployed with an application according to an exemplary embodiment of the present disclosure.
As shown in fig. 7, the present disclosure provides a configuration apparatus 700 for deploying multiple clusters of applications, including:
an obtaining unit 710, configured to obtain a configuration file and a preset cluster list corresponding to an application to be published; 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 the cluster information included in the cluster list; 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 with the application deployed multi-cluster, the inlet controller independent of the cluster is arranged, flow can be controlled according to a unified rule, the flow can be forwarded in a unified mode, and the requirement of a user for unified management of the flow accessing the multi-cluster can be met.
Fig. 8 is a schematic structural diagram of a configuration apparatus of a multi-cluster with an application deployed therein according to another exemplary embodiment of the present disclosure.
As shown in fig. 8, in a multi-cluster configuration apparatus 800 with applications deployed therein provided in the present disclosure, an obtaining unit 810 is similar to the obtaining unit 710 described in fig. 7, and a controller generating unit 820 is similar to the controller generating unit 720 described in fig. 7.
In an optional implementation manner, the obtaining unit 810 is specifically configured to:
the method comprises the steps of obtaining a service configuration file and an entrance configuration file corresponding to an application to be issued, wherein the entrance configuration file is a rule for distributing flow to a cluster, and the service configuration file is a rule for forwarding the flow received by the cluster to a node in the cluster.
In an optional implementation, 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 a node in the cluster;
a controller generating module 822, configured to generate the ingress controller according to the traffic forwarding rule and the cluster information.
In an optional implementation, the obtaining unit 810 is further configured to: acquiring each object configuration file corresponding to each cluster information included in the cluster list according to the cluster list and the application, wherein the object configuration files are files corresponding to the cluster and the application;
the apparatus 800 further includes 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 optional implementation, the obtaining 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 correspond 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 the object configuration information corresponding to each cluster, so as to obtain object configuration files corresponding to each preset cluster.
In an optional embodiment, the object configuration information includes any one of the following information:
application release sequence, and pause information after application release is completed.
In an optional 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 for providing an access address for the cluster.
In an optional embodiment, the apparatus 800 further includes an application deployment unit 840, configured to:
and acquiring the application to be issued, deploying the application in the nodes of each cluster recorded in the cluster list information, and determining a deployment process according to the object of each preset cluster.
Fig. 9 is a schematic structural diagram of a traffic forwarding apparatus in a multi-cluster scenario according to an exemplary embodiment of the present disclosure.
As shown in fig. 9, the traffic forwarding apparatus 900 in a multi-cluster scenario provided by the present disclosure includes:
a receiving unit 910, configured to receive a traffic and analyze the traffic;
a forwarding unit 920, configured to determine, according to a preset ingress controller, a first destination cluster provided with a test node in the multiple clusters and a test node deployed with a test version application if the traffic includes the test parameter; 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 include the test parameters, determining a second destination cluster corresponding to the flow and a destination node in the second destination cluster according to a preset entrance 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 to solve a problem in the prior art that traffic cannot be controlled to access each cluster according to a uniform rule.
In the technical scheme of the disclosure, the collection, storage, use, processing, transmission, provision, disclosure and other processing of the personal information of the related user are all in accordance with the regulations of related laws and regulations and do not violate the good customs of the public order.
The present disclosure also provides an electronic device, a readable storage medium, and a computer program product according to embodiments of the present disclosure.
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 the electronic device can read the computer program, the at least one processor executing the computer program causing the electronic device to perform the solution provided by any of the embodiments described above.
FIG. 10 illustrates a schematic block diagram of an example electronic device 1000 that can 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 phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be examples 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 necessary for the operation of the device 1000 can also be stored. The calculation 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.
A number of 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 a communication unit 1009 such as a network card, a modem, a wireless communication transceiver, or the like. The communication unit 1009 allows the device 1000 to exchange information/data with other devices through a computer network such as the internet and/or various telecommunication networks.
Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuitry, Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), system on a 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 that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.
Program code for implementing the methods of the present disclosure may be written in any combination of one or more programming languages. These program codes 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 codes, when executed by the processor or controller, cause the functions/operations specified in the flowchart and/or block diagram to be performed. 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. A 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 a pointing device (e.g., a mouse or a 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 can 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, speech, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a back-end 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 back-end, 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 clients and servers. A client and server are generally 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 as to solve the defects of high management difficulty and weak service expansibility in the traditional physical host and VPS service ("Virtual Private Server", or simply "VPS"). The server may also be a server of a distributed system, or a server incorporating a blockchain.
It should be understood that various forms of the flows shown above may be used, with steps reordered, added, or deleted. For example, the steps described in the present disclosure may be executed in parallel, sequentially, or in different orders, as long as the desired results of the technical solutions disclosed in the present disclosure can be achieved, and the present disclosure is not limited herein.
The above detailed description should not be construed as limiting the scope of the disclosure. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made in accordance with design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present disclosure should be included in the scope of protection of the present disclosure.
Claims (23)
1. A method of configuring a multi-cluster deployed with an application, comprising:
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 entrance controller according to the configuration file and cluster information included in the cluster list; 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 according to claim 1, wherein the obtaining of the configuration file corresponding to the application to be published comprises:
the method comprises the steps of obtaining a service configuration file and an entrance configuration file corresponding to an application to be issued, wherein the entrance configuration file is a rule for distributing flow to a cluster, and the service configuration file is a rule for forwarding the flow received by the cluster to a node in the cluster.
3. The method of claim 2, wherein the generating an ingress controller from the configuration file and cluster information included in the cluster list comprises:
determining a flow forwarding rule according to a rule for distributing the flow to the cluster and a rule for forwarding the flow received by the cluster to a node in the cluster;
and generating the entrance controller according to the flow forwarding rule and the cluster information.
4. The method of claim 1, further comprising:
acquiring each object configuration file corresponding to each cluster information included in the cluster list according to the cluster list and the application, wherein the object configuration files are files corresponding to the cluster and the application;
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.
5. The method of claim 4, 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 historical 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 object configuration files corresponding to each preset cluster.
6. The method of claim 5, wherein the object configuration information comprises any one of:
application release sequence, and pause information after application release is completed.
7. The method of claim 2 or 3, 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 service; the service is for providing an access address for the cluster.
8. The method of any of claims 1-7, further comprising:
and acquiring the application to be issued, deploying the application in the nodes of each cluster recorded in the cluster list information, and determining a deployment process according to the object of each preset cluster.
9. A traffic forwarding method under a multi-cluster scene comprises the following steps:
receiving flow and analyzing the flow;
if the flow comprises the test parameters, determining a first target cluster provided with test nodes and the test nodes deployed with test version applications in the plurality of clusters according to a preset entrance controller;
forwarding the traffic to a test node of the first destination cluster.
10. The method according to claim 9, wherein if the traffic does not include the 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.
11. A configuration apparatus for deploying multiple clusters of applications, comprising:
the device comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for 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;
the controller generating unit is used for generating an entrance controller according to the configuration file and the cluster information included in the cluster list; 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.
12. The apparatus according to claim 11, wherein the obtaining unit is specifically configured to:
the method comprises the steps of obtaining a service configuration file and an entrance configuration file corresponding to an application to be issued, wherein the entrance configuration file is a rule for distributing flow to a cluster, and the service configuration file is a rule for forwarding the flow received by the cluster to a node in the cluster.
13. The apparatus of claim 12, wherein the controller generates a unit comprising:
the rule generating module is used for determining a flow forwarding rule according to a rule for distributing the flow to the cluster and a rule for forwarding the flow received by the cluster to the nodes in the cluster;
and the controller generation module is used for generating the entrance controller according to the flow forwarding rule and the cluster information.
14. The apparatus of claim 11, wherein:
the acquisition unit is further configured to: acquiring each object configuration file corresponding to each cluster information included in the cluster list according to the cluster list and the application, wherein the object configuration files are files corresponding to the cluster and the application;
the apparatus further includes 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.
15. The apparatus of claim 14, wherein the obtaining 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 applications;
the template determining module is used for determining a file template in the historical 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 object configuration files corresponding to each preset cluster.
16. The apparatus of claim 15, wherein the object configuration information comprises any one of:
application release sequence, and pause information after application release is completed.
17. The apparatus of claim 12 or 13, 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 for providing an access address for the cluster.
18. The apparatus according to any of claims 11-17, further comprising an application deployment unit to:
and acquiring the application to be issued, deploying the application in the nodes of each cluster recorded in the cluster list information, and determining a deployment process according to the object of each preset cluster.
19. A traffic forwarding device under a multi-cluster scene comprises:
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 deploying the test node with a test version application in the plurality of clusters according to a preset entrance controller if the flow comprises the test parameters; forwarding the traffic to a test node of the first destination cluster.
20. The apparatus of claim 19, wherein the forwarding unit is further configured to:
if the flow does not include the test parameters, determining a second destination cluster corresponding to the flow and a destination node in the second destination cluster according to a preset entrance controller; the destination node is deployed with a common version application;
and sending the traffic to the destination node.
21. An electronic device, comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
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-10.
22. A non-transitory computer readable storage medium having stored thereon computer instructions for causing the computer to perform the method of any one of claims 1-10.
23. A computer program product comprising a computer program which, when executed by a processor, carries out the steps of the method of any one of claims 1 to 10.
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 true CN114070889A (en) | 2022-02-18 |
| CN114070889B 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) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115086321A (en) * | 2022-06-14 | 2022-09-20 | 京东科技信息技术有限公司 | Multi-cluster traffic forwarding method and device, and electronic device |
Citations (16)
| 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 |
| US20210281637A1 (en) * | 2020-03-03 | 2021-09-09 | International Business Machines Corporation | Management for a load balancer cluster |
| 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 |
-
2021
- 2021-11-10 CN CN202111327832.0A patent/CN114070889B/en active Active
Patent Citations (16)
| 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 |
| US20210281637A1 (en) * | 2020-03-03 | 2021-09-09 | International Business Machines Corporation | Management for a load balancer cluster |
| 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集群系统的容器网络研究与优化", 信息网络安全, no. 03 * |
| 盛乐标;周庆林;游伟倩;张予倩;: "Kubernetes高可用集群的部署实践", 电脑知识与技术, no. 26 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115086321A (en) * | 2022-06-14 | 2022-09-20 | 京东科技信息技术有限公司 | Multi-cluster traffic forwarding method and device, and electronic device |
| CN115086321B (en) * | 2022-06-14 | 2024-04-05 | 京东科技信息技术有限公司 | Multi-cluster traffic forwarding method and device and electronic equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114070889B (en) | 2023-11-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109408205B (en) | Task scheduling method and device based on hadoop cluster | |
| CN113742031B (en) | Node state information acquisition method and device, electronic equipment and readable storage medium | |
| CN107729176B (en) | Disaster recovery method and disaster recovery system for configuration file management system | |
| CN113641457A (en) | Container creation method, device, apparatus, medium, and program product | |
| US9473304B1 (en) | Generation and distribution of named, definable, serialized tokens | |
| CN113709810B (en) | Method, equipment and medium for configuring network service quality | |
| CN113361838A (en) | Business wind control method and device, electronic equipment and storage medium | |
| CN114911598A (en) | Task scheduling method, device, equipment and storage medium | |
| CN109828830B (en) | Method and apparatus for managing containers | |
| CN114389969A (en) | Client test method and device, electronic equipment and storage medium | |
| CN112817562A (en) | Service processing method and device | |
| CN112398669A (en) | Hadoop deployment method and device | |
| CN114185734A (en) | Cluster monitoring method and device and electronic equipment | |
| US11645109B2 (en) | Managing failures in edge computing environments | |
| CN116325705A (en) | Managing task flows in an edge computing environment | |
| CN114070889A (en) | Configuration method, traffic forwarding method, device, storage medium, and program product | |
| CN115442129A (en) | Method, device and system for managing cluster access authority | |
| CN114756301A (en) | Log processing method, device and system | |
| CN113360689B (en) | Image retrieval system, method, related device and computer program product | |
| US20230325267A1 (en) | Selective privileged container augmentation | |
| CN115981847A (en) | Service grid deployment method and device, electronic equipment and storage medium | |
| CN114356505A (en) | Method, apparatus, device, medium and product for scheduling groups of containers | |
| CN113935613A (en) | Equipment inspection method and device, electronic equipment and computer readable medium | |
| CN115617454A (en) | Containerization service deployment method, device, equipment and storage medium | |
| CN115776489A (en) | Information acquisition method and device, electronic equipment and computer readable 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 |