CN114221773A - Container cloud-based method for automatically adding agents - Google Patents
Container cloud-based method for automatically adding agents Download PDFInfo
- Publication number
- CN114221773A CN114221773A CN202111551795.1A CN202111551795A CN114221773A CN 114221773 A CN114221773 A CN 114221773A CN 202111551795 A CN202111551795 A CN 202111551795A CN 114221773 A CN114221773 A CN 114221773A
- Authority
- CN
- China
- Prior art keywords
- sidecar
- resource object
- field
- adder
- automatic
- 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 abstract description 23
- 238000012544 monitoring process Methods 0.000 claims abstract description 7
- 230000004044 response Effects 0.000 claims description 6
- 238000005516 engineering process Methods 0.000 description 3
- 238000012423 maintenance Methods 0.000 description 3
- 230000008901 benefit Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000002474 experimental method Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000009466 transformation Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/3263—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving certificates, e.g. public key certificate [PKC] or attribute certificate [AC]; Public key infrastructure [PKI] arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
A method for automatically adding an agent based on a container cloud comprises the following operation steps: (1) creating and initializing an automatic sidecar adder into a Kubernetes cluster; (2) after the automatic sidecar adder is successfully initialized, deploying a ConfigMap resource object containing sidecar information in a Kubernetes cluster, monitoring the ConfigMap resource object in the Kubernetes cluster, and storing the sidecar information contained in the ConfigMap resource object; (3) and creating a Pod resource object, and before the Pod resource object is persisted to a Kubernets cluster, if the automatic sidecar adder saves the sidecar specified by the Pod resource object, modifying the Pod resource object description file and adding the specified sidecar information to the Pod resource object description file.
Description
Technical Field
The invention relates to a container cloud-based method for automatically adding agents, and belongs to the technical field of cloud protogenesis.
Background
In recent years, the cloud technology has gradually increased in temperature, and many enterprises have started the way of cloud transformation, and hope to migrate the traditional application to the cloud. In the cloud-native solution, the application is placed in an agile and unchangeable infrastructure to run, so that the application can be seamlessly migrated in different environments, and the mainstream method is realized by a container technology at present. When the containers are large and distributed among different machines, how to manage the large containers becomes a problem. In order to solve the problem, kubernets works as a container arrangement system, which can continuously and automatically manage containerization application, and improve the management efficiency of operation and maintenance personnel.
The sidecar (sidecar) model adds additional functions to the existing service that do not affect the business logic, but rather serve as auxiliary functions, such as collecting logs, managing files. Splitting the service logic and the auxiliary logic into different applications can reduce the degree of coupling between the applications and the complexity of the service, which is an advantage of the sidecar mode. In kubernets (container cloud), it is embodied that each Pod runs multiple containers, which communicate with each other, share a file system, have containers carrying specific service functions, and also have containers serving auxiliary functions, which are called sidecars (i.e. a kind of internal agent). Since the auxiliary functions are common, the sidecars can be multiplexed in multiple Pod resource objects, resulting in a large amount of duplication of the sidecars' information in different Pod resource object description files. The operation and maintenance personnel need to manually add the information of the side cars in each Pod resource object description file, which causes a great deal of data redundancy and reduces the management efficiency.
At present, how to solve the problems of data redundancy and low efficiency caused by manually adding a large amount of repeated sidecar information becomes a technical problem which is urgently needed to be solved in the technical field of cloud and native technology.
Disclosure of Invention
In view of this, the present invention provides a method for automatically adding a sidecar, so as to solve the problems of data redundancy and low efficiency caused by the fact that an operation and maintenance worker manually adds a large amount of repeated sidecar information in each Pod resource object description file.
In order to achieve the above object, the present invention provides a method for automatically adding an agent based on a container cloud, comprising the following operation steps:
step 1, creating and initializing an automatic sidecar adder into a Kubernets cluster;
and 3, creating a Pod resource object to the Kubernets cluster, and modifying the Pod resource object description file and adding the specified sidecar information to the Pod resource object description file if the automatic sidecar adder saves the sidecar specified by the Pod resource object before the Pod resource object is persisted to the Kubernets cluster.
The step 1 further comprises the following steps:
step 11, configuring public key and private key certificates required by TLS connection for the automatic sidecar adder, and a service account number (serviceAccount resource object) having the authority of monitoring the ConfigMap resource object;
step 12, deploying the Deployment and Service resource objects, appointing parameters of the automatic sidecar adder, and starting the Service of the automatic sidecar adder, wherein the parameters of the automatic sidecar adder comprise: label key value pairs required to be met by the monitored ConfigMap resource objects and a Pod resource object specify an annotation name space for adding a sidecar;
step 13, configuring an event matching rule for creating the Pod resource object, a service reference of the automatic sidecar adder, and a CA certificate for verifying TLS connection of the automatic sidecar adder service by deploying the mutetgWebhookconfiguration resource object.
In the step 2, the automatic sidecar adder monitors the ConfigMap resource object in kubernets, and stores the specific content of the sidecar information contained in the object:
the automatic side car adder monitors the ConfigMap resource objects meeting the corresponding label key value pairs, if the data of the ConfigMap resource objects meet the format of side car information, the ConfigMap resource objects are stored, and the names of the side cars are used as unique identifications of the side cars; the sidecar information contains the following fields: name, contacts, initcontacts, volumes Mounts, env, hostAliases, serviceAccountName; the name field represents the name of the side car, is in a character string format, is a mandatory field and is used as the unique identifier of the side car; the other fields are specific information of the side car and are optional fields;
contacts field: the sidecar comprises a Container which can contain a plurality of containers and is in a Container v1 core format;
initContainers field: the sidecar comprises an initial Container which comprises a plurality of initial containers and is in a Container v1 core format;
the volumes field: the side car comprises a Volume which comprises a plurality of volumes and is in a Volume v1 core format;
volume Mounts field: the volume mount contained in the sidecar can contain a plurality of volume mounts, and is in a VolumeMount v1 core format;
env field: the environment variable contained in the sidecar can contain a plurality of environment variables and is in an EnvVar v1 core format;
hostlias field: the host alias contained in the sidecar can contain a plurality of host aliases and is in a HostAlias v1 core format;
serviceAccountName field: the service account name contained in the side car is in a character string format.
The step 3 further comprises the following steps:
step 31, writing an annotation key value pair for appointing to add a side car into the Pod resource object description file, wherein the key appoints an annotation name space for adding the side car for the Pod resource object, namely a preset parameter of the automatic side car adder, and the value is the name of the side car; the concrete writing method of the annotation key value pair for specifying the adding of the sidecar is as follows:
< Pod resource object specifies add sidecar's annotation namespace >/request 1; a sidecar 2; ...; the values of the sidecar n annotation key value pair can specify a plurality of sidecars which are separated by semicolons;
step 32, recognizing a creation event of a Pod resource object by a native mutedassionsWebhook controller in a Kubernetes cluster, and calling the automatic sidecar adder service to add a sidecar to the Pod resource object;
step 33, the automatic sidecar adder resolves the transmitted request into a Pod resource object description file, identifies the annotation key value pair of the appointed sidecar, searches for sidecar information according to the name of the sidecar, adds the sidecar information to the Pod resource object description file according to the specified field merging rule if the sidecar information exists, constructs a response of the modified Pod resource object description file, and returns the response to the muttingAdmissionWebhook controller; the automatic sidecar adder adds a plurality of sidecar information to the Pod resource object description file from left to right according to the value of the specified sidecar annotation key value pair; after the side car information is successfully added, the automatic side car adder adds an annotation key value pair of the Pod resource object description file to indicate that the side car information is successfully added, and the specific writing method is as follows:
< Pod resource object specifies the annotation namespace >/inserted: true of adding the sidecar.
The field merging rule in step 33 is:
contacts field: merging with spec.contacts field of Pod resource object, if there is duplicate name container, reporting error and abandoning merging;
initContainers field: merging with spec. initcontainers field of Pod resource object, if there is duplicate initial container, reporting error and abandoning merging;
the volumes field: merging with spec. volumes field of Pod resource object, if there is duplicate name volume, reporting error and abandoning merging;
volume Mounts field: merging with spec.contacts.volumemount and spec.initcontacts.volumemount fields of the Pod resource object respectively, and if the duplicate volume is mounted, not replacing;
env field: respectively merging with spec.contacts [. env ] and spec.initcontacts [. env ] fields of the Pod resource objects, and if the duplicate name environment variables exist, not replacing;
hostlias field: merging with spec. hostAliases field of the Pod resource object, even if there is a repeated ip field, merging in the same way;
serviceAccountName field: and if the spec.serviceAccountName field of the Pod resource object is null or default, replacing the spec.serviceAccountName field, and otherwise, not replacing the spec.serviceAccountName field.
The invention has the beneficial effects that: the invention creates an automatic sidecar adder based on the access control mechanism of Kubernets, which can add sidecar information to a Pod resource object according to annotations before the Pod resource object is persisted to a Kubernets cluster, and finally the Pod resource object added with a sidecar can be persisted to the Kubernets cluster and started.
Drawings
FIG. 1 is a schematic flow chart of a method for automatically adding an agent based on a container cloud according to the present invention;
FIG. 2 is a deployment diagram of a method for automatically adding an agent based on a container cloud in an embodiment of the present invention;
fig. 3 is an example of the format of the sidecar information in the embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention are described in detail below with reference to the accompanying drawings.
Referring to fig. 1 and 2, the present invention provides a method for automatically adding an agent based on a container cloud, including the following operation steps:
step 1, creating and initializing an automatic sidecar adder into a Kubernets cluster;
and 3, creating a Pod resource object to the Kubernets cluster, and modifying the Pod resource object description file and adding the specified sidecar information to the Pod resource object description file if the automatic sidecar adder saves the sidecar specified by the Pod resource object before the Pod resource object is persisted to the Kubernets cluster.
The step 1 further comprises the following steps:
step 11, configuring public key and private key certificates required by TLS connection for the automatic sidecar adder, and a service account number (serviceAccount resource object) having the authority of monitoring the ConfigMap resource object;
step 12, deploying the Deployment and Service resource objects, appointing parameters of the automatic sidecar adder, and starting the Service of the automatic sidecar adder, wherein the parameters of the automatic sidecar adder comprise: label key value pairs required to be met by the monitored ConfigMap resource objects and a Pod resource object specify an annotation name space for adding a sidecar;
the embodiment specifies the tag key value pair that the monitorable ConfigMap resource object needs to satisfy: if the app is sidecar, the ConfigMap resource object that satisfies the set of sidecar tag key value pairs is monitored by the automatic sidecar adder.
In this embodiment, the Pod resource object is specified to add the annotation namespace of the sidecar: sidecar, then the key contains an annotated key-value pair of "sidecar," whose value specifies the added sidecar name for the Pod resource object.
Step 13, configuring an event matching rule for creating the Pod resource object, a service reference of the automatic sidecar adder, and a CA certificate for verifying TLS connection of the automatic sidecar adder service by deploying the mutetgWebhookconfiguration resource object.
In the step 2, the automatic sidecar adder monitors the ConfigMap resource object in kubernets, and stores the specific content of the sidecar information contained in the object:
the automatic side car adder monitors the ConfigMap resource objects meeting the corresponding label key value pairs (preset parameters of the automatic side car adder), if the data of the ConfigMap resource objects meet the format of side car information, the ConfigMap resource objects are stored, and the names of the side cars are used as unique identification of the side cars;
an example of the format of the sidecar information is shown in fig. 3, and the sidecar information includes the following fields: name, contacts, initcontacts, volumes Mounts, env, hostAliases, serviceAccountName; the name field represents the name of the side car, is in a character string format, is a mandatory field and is used as the unique identifier of the side car; the other fields are specific information of the side car and are optional fields;
contacts field: the sidecar comprises a Container which can contain a plurality of containers and is in a Container v1 core format;
initContainers field: the sidecar comprises an initial Container which comprises a plurality of initial containers and is in a Container v1 core format;
the volumes field: the side car comprises a Volume which comprises a plurality of volumes and is in a Volume v1 core format;
volume Mounts field: the volume mount contained in the sidecar can contain a plurality of volume mounts, and is in a VolumeMount v1 core format;
env field: the environment variable contained in the sidecar can contain a plurality of environment variables and is in an EnvVar v1 core format;
hostlias field: the host alias contained in the sidecar can contain a plurality of host aliases and is in a HostAlias v1 core format;
serviceAccountName field: the service account name contained in the side car is in a character string format.
The step 3 further comprises the following steps:
step 31, writing an annotation key value pair for appointing to add a side car into the Pod resource object description file, wherein the key appoints an annotation name space for adding the side car for the Pod resource object, namely a preset parameter of the automatic side car adder, and the value is the name of the side car; the concrete writing method of the annotation key value pair for specifying the adding of the sidecar is as follows:
< Pod resource object specifies add sidecar's annotation namespace >/request 1; a sidecar 2; ...; the values of the sidecar n annotation key value pair can specify a plurality of sidecars which are separated by semicolons;
in this embodiment, the annotation key-value pair is: sidecar/request sidecar 1; sidecar2, i.e., specifies the addition of sidecars named sidecar1 and sidecar 2.
Step 32, recognizing a creation event of a Pod resource object by a native mutedassionsWebhook controller in a Kubernetes cluster, and calling the automatic sidecar adder service to add a sidecar to the Pod resource object;
step 33, the automatic sidecar adder resolves the transmitted request into a Pod resource object description file, identifies the annotation key value pair of the appointed sidecar, searches for sidecar information according to the name of the sidecar, adds the sidecar information to the Pod resource object description file according to the specified field merging rule if the sidecar information exists, constructs a response of the modified Pod resource object description file, and returns the response to the muttingAdmissionWebhook controller;
the automatic sidecar adder adds a plurality of sidecar information to the Pod resource object description file from left to right according to the value of the specified sidecar annotation key value pair; after the side car information is successfully added, the automatic side car adder adds an annotation key value pair of the Pod resource object description file to indicate that the side car information is successfully added, and the specific writing method is as follows:
< Pod resource object specifies the Annotation namespace of Add sidecar >/inserted: true
In this embodiment, the annotation key-value pair is: sidecar/inserted: true.
The field merging rule in step 33 is:
contacts field: merging with spec.contacts field of Pod resource object, if there is duplicate name container, reporting error and abandoning merging;
initContainers field: merging with spec. initcontainers field of Pod resource object, if there is duplicate initial container, reporting error and abandoning merging;
the volumes field: merging with spec. volumes field of Pod resource object, if there is duplicate name volume, reporting error and abandoning merging;
volume Mounts field: merging with spec.contacts.volumemount and spec.initcontacts.volumemount fields of the Pod resource object respectively, and if the duplicate volume is mounted, not replacing;
env field: merging with spec.contacts [. env ] and spec.initcontacts [. env ] fields of the Pod resource object (environment variables of each container and the initial container of the Pod resource object), respectively, and if the environment variables are renamed, not replacing;
hostlias field: merging with spec. hostAliases field of the Pod resource object, even if there is a repeated ip field, merging in the same way;
serviceAccountName field: and if the spec, serviceaccountname field of the Pod resource object is null or default, replacing the Pod resource object (corresponding replacement can also occur to the volume and the volume mount related to the service account in the Pod resource object), otherwise, not replacing the Pod resource object.
The inventor conducts a large number of experiments on the method, and experimental results prove that the method effectively solves the problems of data redundancy and low efficiency caused by manually adding a large number of repeated sidecar information.
Claims (5)
1. A method for automatically adding an agent based on a container cloud comprises the following operation steps:
step 1, creating and initializing an automatic sidecar adder into a Kubernets cluster;
step 2, after the automatic sidecar adder is initialized successfully, deploying a ConfigMap resource object containing sidecar information in a Kubernets cluster, and monitoring the ConfigMap resource object in the Kubernets by the automatic sidecar adder and storing the sidecar information contained in the ConfigMap resource object;
and 3, creating a Pod resource object to the Kubernets cluster, and modifying the Pod resource object description file and adding the specified sidecar information to the Pod resource object description file if the automatic sidecar adder saves the sidecar specified by the Pod resource object before the Pod resource object is persisted to the Kubernets cluster.
2. The method for automatically adding the agent based on the container cloud as claimed in claim 1, wherein the step 1 further comprises:
step 11, configuring public key and private key certificates required by TLS connection for the automatic sidecar adder, and a service account number (serviceAccount resource object) having the authority of monitoring the ConfigMap resource object;
step 12, deploying the Deployment and Service resource objects, appointing parameters of the automatic sidecar adder, and starting the Service of the automatic sidecar adder, wherein the parameters of the automatic sidecar adder comprise: label key value pairs required to be met by the monitored ConfigMap resource objects and a Pod resource object specify an annotation name space for adding a sidecar;
step 13, configuring an event matching rule for creating the Pod resource object, a service reference of the automatic sidecar adder, and a CA certificate for verifying TLS connection of the automatic sidecar adder service by deploying the mutetgWebhookconfiguration resource object.
3. The method for automatically adding the agent based on the container cloud as claimed in claim 1, wherein the automatic sidecar adder in step 2 monitors a ConfigMap resource object in kubernets and stores the specific content of the sidecar information contained therein as follows:
the automatic side car adder monitors the ConfigMap resource objects meeting the corresponding label key value pairs, if the data of the ConfigMap resource objects meet the format of side car information, the ConfigMap resource objects are stored, and the names of the side cars are used as unique identifications of the side cars; the sidecar information contains the following fields: name, contacts, initcontacts, volumes Mounts, env, hostAliases, serviceAccountName; the name field represents the name of the side car, is in a character string format, is a mandatory field and is used as the unique identifier of the side car; the other fields are specific information of the side car and are optional fields;
contacts field: the sidecar comprises a Container which can contain a plurality of containers and is in a Container v1 core format;
initContainers field: the sidecar comprises an initial Container which comprises a plurality of initial containers and is in a Container v1 core format;
the volumes field: the side car comprises a Volume which comprises a plurality of volumes and is in a Volume v1 core format;
volume Mounts field: the volume mount contained in the sidecar can contain a plurality of volume mounts, and is in a VolumeMount v1 core format;
env field: the environment variable contained in the sidecar can contain a plurality of environment variables and is in an EnvVar v1 core format;
hostlias field: the host alias contained in the sidecar can contain a plurality of host aliases and is in a HostAlias v1 core format;
serviceAccountName field: the service account name contained in the side car is in a character string format.
4. The method for automatically adding an agent based on the container cloud as claimed in claim 1, wherein the step 3 further comprises:
step 31, writing an annotation key value pair for appointing to add a side car into the Pod resource object description file, wherein the key appoints an annotation name space for adding the side car for the Pod resource object, namely a preset parameter of the automatic side car adder, and the value is the name of the side car; the concrete writing method of the annotation key value pair for specifying the adding of the sidecar is as follows:
< Pod resource object specifies add sidecar's annotation namespace >/request 1; a sidecar 2; ...; the values of the sidecar n annotation key value pair can specify a plurality of sidecars which are separated by semicolons;
step 32, recognizing a creation event of a Pod resource object by a native mutedassionsWebhook controller in a Kubernetes cluster, and calling the automatic sidecar adder service to add a sidecar to the Pod resource object;
step 33, the automatic sidecar adder resolves the transmitted request into a Pod resource object description file, identifies the annotation key value pair of the appointed sidecar, searches for sidecar information according to the name of the sidecar, adds the sidecar information to the Pod resource object description file according to the specified field merging rule if the sidecar information exists, constructs a response of the modified Pod resource object description file, and returns the response to the muttingAdmissionWebhook controller; the automatic sidecar adder adds a plurality of sidecar information to the Pod resource object description file from left to right according to the value of the specified sidecar annotation key value pair; after the side car information is successfully added, the automatic side car adder adds an annotation key value pair of the Pod resource object description file to indicate that the side car information is successfully added, and the specific writing method is as follows:
< Pod resource object specifies the annotation namespace >/inserted: true of adding the sidecar.
5. The method for automatically adding an agent based on the container cloud according to claim 4, wherein the field merging rule in the step 33 is:
contacts field: merging with spec.contacts field of Pod resource object, if there is duplicate name container, reporting error and abandoning merging;
initContainers field: merging with spec. initcontainers field of Pod resource object, if there is duplicate initial container, reporting error and abandoning merging;
the volumes field: merging with spec. volumes field of Pod resource object, if there is duplicate name volume, reporting error and abandoning merging;
volume Mounts field: merging with spec.contacts.volumemount and spec.initcontacts.volumemount fields of the Pod resource object respectively, and if the duplicate volume is mounted, not replacing;
env field: respectively merging with spec.contacts [. env ] and spec.initcontacts [. env ] fields of the Pod resource objects, and if the duplicate name environment variables exist, not replacing;
hostlias field: merging with spec. hostAliases field of the Pod resource object, even if there is a repeated ip field, merging in the same way;
serviceAccountName field: and if the spec.serviceAccountName field of the Pod resource object is null or default, replacing the spec.serviceAccountName field, and otherwise, not replacing the spec.serviceAccountName field.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111551795.1A CN114221773B (en) | 2021-12-17 | 2021-12-17 | Method for automatically adding agent based on container cloud |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111551795.1A CN114221773B (en) | 2021-12-17 | 2021-12-17 | Method for automatically adding agent based on container cloud |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114221773A true CN114221773A (en) | 2022-03-22 |
| CN114221773B CN114221773B (en) | 2024-02-06 |
Family
ID=80703595
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111551795.1A Active CN114221773B (en) | 2021-12-17 | 2021-12-17 | Method for automatically adding agent based on container cloud |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114221773B (en) |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110262899A (en) * | 2019-06-20 | 2019-09-20 | 无锡华云数据技术服务有限公司 | Monitor component elastic telescopic method, apparatus and controlled terminal based on Kubernetes cluster |
| CN110535831A (en) * | 2019-07-30 | 2019-12-03 | 平安科技（深圳）有限公司 | Cluster safety management method, device and storage medium based on Kubernetes and network domains |
| US20200133789A1 (en) * | 2018-10-25 | 2020-04-30 | EMC IP Holding Company LLC | Application consistent snapshots as a sidecar of a containerized application |
| CN111212129A (en) * | 2019-12-30 | 2020-05-29 | 北京浪潮数据技术有限公司 | Container application high-availability method, device and equipment based on side car mode |
| US20200186422A1 (en) * | 2018-12-10 | 2020-06-11 | Sap Se | Using a container orchestration service for dynamic routing |
| CN111865971A (en) * | 2020-07-17 | 2020-10-30 | 成都三零凯天通信实业有限公司 | Kubernetes service container security detection method based on sidecar scheme |
| WO2020253347A1 (en) * | 2019-06-17 | 2020-12-24 | 深圳前海微众银行股份有限公司 | Container cluster management method, device and system |
| CN112506617A (en) * | 2020-12-16 | 2021-03-16 | 新浪网技术(中国)有限公司 | Mirror image updating method and device for sidecar container in Kubernetes cluster |
| CN112596762A (en) * | 2020-12-16 | 2021-04-02 | 中国建设银行股份有限公司 | Rolling upgrading method and device |
| CN112929180A (en) * | 2021-02-05 | 2021-06-08 | 中国—东盟信息港股份有限公司 | Kubernetes zero trust network security system and implementation method thereof |
-
2021
- 2021-12-17 CN CN202111551795.1A patent/CN114221773B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20200133789A1 (en) * | 2018-10-25 | 2020-04-30 | EMC IP Holding Company LLC | Application consistent snapshots as a sidecar of a containerized application |
| US20200186422A1 (en) * | 2018-12-10 | 2020-06-11 | Sap Se | Using a container orchestration service for dynamic routing |
| WO2020253347A1 (en) * | 2019-06-17 | 2020-12-24 | 深圳前海微众银行股份有限公司 | Container cluster management method, device and system |
| CN110262899A (en) * | 2019-06-20 | 2019-09-20 | 无锡华云数据技术服务有限公司 | Monitor component elastic telescopic method, apparatus and controlled terminal based on Kubernetes cluster |
| CN110535831A (en) * | 2019-07-30 | 2019-12-03 | 平安科技（深圳）有限公司 | Cluster safety management method, device and storage medium based on Kubernetes and network domains |
| CN111212129A (en) * | 2019-12-30 | 2020-05-29 | 北京浪潮数据技术有限公司 | Container application high-availability method, device and equipment based on side car mode |
| CN111865971A (en) * | 2020-07-17 | 2020-10-30 | 成都三零凯天通信实业有限公司 | Kubernetes service container security detection method based on sidecar scheme |
| CN112506617A (en) * | 2020-12-16 | 2021-03-16 | 新浪网技术(中国)有限公司 | Mirror image updating method and device for sidecar container in Kubernetes cluster |
| CN112596762A (en) * | 2020-12-16 | 2021-04-02 | 中国建设银行股份有限公司 | Rolling upgrading method and device |
| CN112929180A (en) * | 2021-02-05 | 2021-06-08 | 中国—东盟信息港股份有限公司 | Kubernetes zero trust network security system and implementation method thereof |
Non-Patent Citations (2)
| Title |
|---|
| 李铭轩;童俊杰;刘秋妍;: "基于云原生的5G核心网演进解决方案研究", 信息通信技术, no. 01 * |
| 王焘: "一种面向异常传播的微服务故障诊断方法", 《计算机科学》 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114221773B (en) | 2024-02-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2022022477A1 (en) | Management operation and maintenance platform and data processing method | |
| EP3709227B1 (en) | System and method for interoperable communication of an automation system component with multiple information sources | |
| US8656412B2 (en) | Pipeline across isolated computing environments | |
| CN109918359B (en) | Database service persistence method and system based on sweep | |
| US10623262B2 (en) | Methods and systems to adjust a monitoring tool and auxiliary servers of a distributed computing system | |
| EP2442489A1 (en) | Distributed management monitoring system, monitoring method and creating method thereof | |
| US20170371568A1 (en) | Failure resistent volume creation in a shared storage environment | |
| CN107797767A (en) | One kind is based on container technique deployment distributed memory system and its storage method | |
| CN109677465B (en) | Distributed real-time system architecture for rail transit integrated monitoring system | |
| US11811839B2 (en) | Managed distribution of data stream contents | |
| CN109923835B (en) | Local and off-site communications | |
| CN113032356A (en) | Cabin distributed file storage system and implementation method | |
| CN112328697A (en) | Data synchronization method based on big data | |
| CN115640110A (en) | Distributed cloud computing system scheduling method and device | |
| CN113315754A (en) | Intelligent linkage method, device, equipment and medium for firewall of container visit | |
| CN114374701B (en) | Transparent sharing device for sample model of multistage linkage artificial intelligent platform | |
| CN114221773A (en) | Container cloud-based method for automatically adding agents | |
| CN112395308A (en) | Data query method based on HDFS database | |
| CN112416656B (en) | Data offline storage method for station application server | |
| CN113641760A (en) | Data synchronization method and device | |
| US20210072895A1 (en) | Replication Configuration for Multiple Heterogeneous Data Stores | |
| CN109947451A (en) | A kind of cluster application file updating method, system, medium and equipment | |
| CN115250197B (en) | Device for automatically creating container discovery service | |
| CN113127592B (en) | Distributed storage system | |
| CN111797062B (en) | Data processing method, device and distributed database system |
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 |