CN112398936B - Kubernetes-based multi-network card container implementation method and system - Google Patents
Kubernetes-based multi-network card container implementation method and system Download PDFInfo
- Publication number
- CN112398936B CN112398936B CN202011227634.2A CN202011227634A CN112398936B CN 112398936 B CN112398936 B CN 112398936B CN 202011227634 A CN202011227634 A CN 202011227634A CN 112398936 B CN112398936 B CN 112398936B
- Authority
- CN
- China
- Prior art keywords
- plug
- network
- container
- module
- reading
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
- H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- 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
-
- 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/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- 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/50—Network services
- H04L67/56—Provisioning of proxy services
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45595—Network integration; Enabling network access in virtual machine instances
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/50—Reducing energy consumption in communication networks in wire-line communication networks, e.g. low power modes or reduced link rate
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Computer Security & Cryptography (AREA)
- Health & Medical Sciences (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a Kubernetes-based multi-network-card container implementation method and a Kubernetes-based multi-network-card container implementation system, and belongs to the technical field of container multi-network cards; the method comprises the following specific steps: s1, reading and sequencing all container network plug-ins under a container network interface configuration catalog by using the network plug-ins; s2, loading and checking the container network configuration file, defining by using a CNI standard format and using an expanded network plug-in as a default network plug-in of a container manager; s3, acquiring default network plug-in information, and calling the default network plug-in to complete an IP distribution function; s4, a network plug-in supporting multiple networks is manufactured to act on the basis of the container network interface machine; by using the method, the cloud multi-network-card function of the wave container is realized, the network is ensured to be special, and the network security of multiple tenants is improved.
Description
Technical Field
The invention discloses a Kubernetes-based multi-network-card container implementation method and system, and relates to the technical field of container multi-network cards.
Background
Kubernets is a brand-new container technology-based distributed architecture leading scheme, provides a series of functions such as deployment and operation, resource scheduling, service discovery and dynamic scaling for containerized applications, and improves convenience and high availability of large-scale container cluster management.
When the tenant application runs in the container cloud in the container form, the tenant access to the container can be realized through a service, for example, access to the container cloud node IP and a service port is realized through the node IP as a proxy. Inside the container cloud, the access between containers is not blocked, and the implementation mode is low in safety for the tenants. For tenants, a network similar to a VPC needs to be used, and even inside a container cloud, the containers cannot be accessed mutually, so that the safety of tenant containers is improved. However, actions like state collection of containers also require a network that requires all containers to be accessible inside the container cloud. For the container cloud, the container operation of multiple network cards needs to be supported at the same time, so that the normal operation of the container is ensured, and the availability of a special service network is also ensured;
therefore, the invention provides a Kubernetes-based multi-network card container implementation method and a Kubernetes-based multi-network card container implementation system to solve the problems.
Disclosure of Invention
Aiming at the problems in the prior art, the invention provides a multi-network card container implementation method and a system based on Kubernets, and the adopted technical scheme is as follows: a multi-network card container implementation method based on Kubernetes comprises the following specific steps:
s1, reading and sequencing all container network plug-ins in a container network interface configuration directory by using network plug-ins;
s2, loading and verifying a container network configuration file, defining by using a CNI standard format, and using an expanded network plug-in as a container manager default network plug-in;
s3, acquiring the information of the default network plug-in, calling the default network plug-in to complete the IP distribution function:
s301, reading the comments of the container group to obtain the default network plug-in and the additional network plug-in information;
s302, caching network plug-in information on a band node;
s303, recursively calling an adding command of the proxy plug-in to complete the network card generation and IP distribution functions of the network plug-in;
s304, returning an execution result to the network plug-in;
s4, a network plug-in supporting multiple networks is manufactured to act on the basis of the container network interface machine:
s401, generating a Multus configuration file by using an initialization script;
s402, reading the existing network plug-ins of the current container cloud cluster;
s403 uses the read first network plug-in as a default proxy plug-in.
S303, recursively calling the deleting command of the proxy plug-in by reading the cached container proxy network plug-in information to complete the network card deleting and IP recovering functions of the corresponding network plug-in
A multi-network card container implementation system based on Kubernetes specifically comprises a plug-in reading module, a plug-in definition module, a plug-in distribution module and a plug-in manufacturing module:
a plug-in reading module: reading and sequencing all container network plug-ins under a container network interface configuration catalog by utilizing the network plug-ins;
a plug-in definition module: loading and checking a container network configuration file, defining by using a CNI standard format and using an expanded network plug-in as a default network plug-in of a container manager;
a plug-in distribution module: acquiring default network plug-in information, and calling the default network plug-in to complete an IP distribution function;
the plug-in distribution module specifically comprises an information reading module, an information caching module, a function setting module and an execution returning module:
an information reading module: acquiring default network plug-in and additional network plug-in information by reading the comments of the container group;
the information caching module: caching network plug-in information on the tape node;
a function setting module: recursively calling an adding command of the proxy plug-in to realize network card generation and IP distribution functions of the network plug-in;
an execution return module: returning an execution result to the network plug-in;
a plug-in manufacturing module: a network plug-in supporting multiple networks is manufactured to carry out proxy based on the container network interface machine;
the plug-in manufacturing module specifically comprises a configuration generation module, a plug-in reading module and a plug-in application module:
a configuration generation module: generating a configuration file of Multus by using the initialization script;
a plug-in reading module: reading an existing network plug-in of a current container cloud cluster;
a plug-in application module: and using the read first network plug-in as a default proxy plug-in.
The function setting module recursively calls a deleting command of the proxy plug-in by reading the cached container proxy network plug-in information to complete the network card deleting and IP recycling functions of the corresponding network plug-in.
The beneficial effects of the invention are as follows: when the method is used in the wave container manager, the wave container manager only uses one container network plug-in, when the container manager is started, the network plug-ins are loaded according to S1, all the container network plug-ins under the container network interface configuration catalog are read, and the container network plug-ins are arranged in an ascending order according to file names; then loading a first container network configuration file according to S2, using CNI standard format definition after verification is passed, and using the CNI standard format definition as a container manager default network plug-in; when the container manager creates a container group, acquiring the information of the default network plug-in according to the S3, and calling the default network plug-in to complete the functions of IP allocation and the like; finally, a network plug-in supporting multiple networks is manufactured to act on the basis of the container network interface machine according to the step S4; by using the method, the cloud multi-network-card function of the surge container is realized, the special purpose of the network is ensured, and the network security of multi-tenants is improved.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and those skilled in the art can obtain other drawings based on the drawings without inventive labor.
FIG. 1 is a flow chart of the method of the present invention; FIG. 2 is a schematic diagram of the system of the present invention; FIG. 3 is a schematic diagram of the application connection of the present invention; FIG. 4 is a schematic diagram of a technical architecture of a network proxy plugin; fig. 5 is a schematic diagram of the operation of the application of the present invention.
Detailed Description
The present invention is further described below in conjunction with the following figures and specific examples so that those skilled in the art may better understand the present invention and practice it, but the examples are not intended to limit the present invention.
The container technology is a relatively popular PaaS technology for providing micro services, kubernets are the most popular container arrangement management technology in recent times, a cloud platform for providing containers based on Kubernets is the first choice of various cloud manufacturers, when an application of a tenant runs in a container cloud in a container form, the tenant can access the container through services, such as access to a container cloud node IP and a service port, and the like, but the access is realized by taking a node IP as an agent. Inside the container cloud, the inter-container access is free of any obstacles, and in such an implementation, the security is low for the tenant. For the tenant, a network similar to a VPC needs to be used, so that even inside a container cloud, the containers cannot be accessed to each other, and the security of the tenant container is improved. However, actions like state collection of containers also require a network that requires all containers to be accessible inside the container cloud. For the container cloud, the container operation of multiple network cards needs to be supported at the same time, so that the normal operation of the container is ensured, and the availability of a special service network is also ensured;
first, the term involved is annotated:
PaaS is a platform as a service;
kubernets: a container orchestration management component;
VPC: a virtual private cloud;
macvlan: virtualizing a plurality of network plug-ins of the virtual network cards from a certain physical network card;
and (4) Calico: a three-tier based container network plug-in;
multus: a container network proxy plug-in;
the first embodiment is as follows:
a multi-network card container implementation method based on Kubernetes comprises the following specific steps:
s1, reading and sequencing all container network plug-ins under a container network interface configuration catalog by using the network plug-ins;
s2, loading and verifying a container network configuration file, defining by using a CNI standard format, and using an expanded network plug-in as a container manager default network plug-in;
s3, acquiring information of the default network plug-in, and calling the default network plug-in to complete an IP distribution function;
s4, a network plug-in supporting multiple networks is manufactured to act on the basis of the container network interface machine;
when the method is used in the wave container manager, the wave container manager only uses one container network plug-in, when the container manager is started, the network plug-ins are loaded according to S1, all the container network plug-ins under the container network interface configuration catalog are read, and the container network plug-ins are arranged in an ascending order according to file names; then loading a first container network configuration file according to S2, using CNI standard format definition after verification is passed, and using the CNI standard format definition as a container manager default network plug-in; when the container manager creates a container group, acquiring default network plug-in information according to S3, and calling the default network plug-in to complete functions such as IP distribution and the like; finally, a network plug-in supporting multiple networks is manufactured to act on the basis of the container network interface machine according to the step S4; by using the method, the cloud multi-network-card function of the wave container is realized, the network is ensured to be special, and the network security of multiple tenants is improved;
further, the step S3 of acquiring information of the default network plug-in and calling the default network plug-in to complete the IP distribution function includes the following specific steps;
s301, acquiring default network plug-ins and additional network plug-in information by reading comments of the container group;
s302, caching network plug-in information on a band node;
s303, recursively calling an adding command of the proxy plug-in to complete network card generation and IP distribution functions of the network plug-in;
s304, returning an execution result to the network plug-in;
the adding command is used for generating a network card and distributing IP (Internet protocol) for the designated container group, firstly reading notes of the container group according to S301, acquiring information of a default network plug-in and an additional network plug-in, including information such as bandwidth limitation and port mapping, caching the information on the nodes according to S302 after reading the information, then recursively calling the adding command of the proxy plug-in according to S303, completing functions such as generating the network card corresponding to the network plug-in, distributing the IP and the like, and returning an execution result of the main network plug-in;
further, in S303, the network card deletion and IP recovery functions of the corresponding network card are completed by reading cached container proxy network card information and recursively invoking a deletion command of the proxy card;
the deleting command is used for deleting the network card and recovering the IP for the specified container group, and the deleting command of the proxy plug-in is recursively called by reading the cached container proxy network plug-in information according to the S303 so as to complete the functions of deleting the network card and recovering the IP and the like of the corresponding network plug-in;
further, the step S4 of making a Multus plugin supporting multiple networks for proxy based on the container network interface machine includes the following specific steps;
s401, generating a Multus configuration file by using an initialization script;
s402, reading existing network plug-ins of the current container cloud cluster;
s403 uses the read first network plug-in as a default proxy plug-in.
Initializing a script according to S401 to generate a configuration file of Multus, wherein the file name is 00-multus.conf, ensuring that the container manager uses Multus as a default network plug-in, reading the existing network plug-in of the current container cloud cluster according to S402, and using the read first network plug-in as a default proxy plug-in according to S403.
A network plug-in agent is manufactured based on a container network interface machine, a plurality of networks are supported, and the network plug-in agent is realized through a network plug-in agent mechanism, for example, multus is a network proxy plug-in; multus is a network plug-in written based on a container network interface standard, and can realize the cyclic calling of other network plug-ins, thereby generating a plurality of network cards for a container group.
Example two:
a multi-network card container implementation system based on Kubernetes specifically comprises a plug-in reading module, a plug-in definition module, a plug-in distribution module and a plug-in manufacturing module:
a plug-in reading module: reading all container network plug-ins in a container network interface configuration directory by using the network plug-ins and sequencing the container network plug-ins;
a plug-in definition module: loading and checking a container network configuration file, defining by using a CNI standard format and using an expanded network plug-in as a default network plug-in of a container manager;
a plug-in distribution module: acquiring information of a default network plug-in, and calling the default network plug-in to complete an IP distribution function;
a plug-in manufacturing module: a network plug-in supporting multiple networks is made to act on the basis of a container network interface machine;
when the system is used in the wave container manager, the wave container manager only uses one container network plug-in, when the container manager is started, the plug-in reading module is used for loading the network plug-ins, reading all the container network plug-ins under the container network interface configuration directory, and arranging the container network plug-ins in an ascending order according to file names; then, loading a first container network configuration file through a plug-in definition module, using CNI standard format definition after verification is passed, and using the CNI standard format definition as a container manager default network plug-in; when the container manager creates a container group, acquiring default network plug-in information through a plug-in allocation module, and calling the default network plug-in to complete functions such as IP allocation; finally, a network plug-in supporting multiple networks is manufactured by using a plug-in manufacturing module based on a container network interface machine for proxy; by using the method, the cloud multi-network-card function of the surge container is realized, the special purpose of the network is ensured, and the network security of multi-tenants is improved;
further, the plug-in distribution module specifically includes an information reading module, an information caching module, a function setting module, and an execution return module:
an information reading module: acquiring default network plug-in and additional network plug-in information by reading the comments of the container group;
the information caching module: caching network plug-in information on the tape node;
a function setting module: recursively calling an adding command of the proxy plug-in to realize network card generation and IP distribution functions of the network plug-in;
an execution return module: returning an execution result to the network plug-in;
the adding command is used for generating a network card and distributing IP (Internet protocol) for a specified container group, firstly, notes of the container group are read through an information reading module, information of a default network plug-in and an additional network plug-in, including information such as bandwidth limitation and port mapping, is obtained, is cached on a node by using an information caching module after being read, then, a function setting module is used for recursively calling the adding command of the proxy plug-in to complete functions such as generating the network card corresponding to the network plug-in and distributing IP (Internet protocol), and finally, an execution returning module is used for returning an execution result of the main network plug-in;
furthermore, the function setting module recursively calls a deleting command of the proxy plug-in by reading the cached container proxy network plug-in information to complete the network card deleting and IP recycling functions of the corresponding network plug-in;
the deleting command is used for deleting the network card and recovering the IP for the specified container group, and the function setting module recursively calls the deleting command of the proxy plug-in by reading the cached container proxy network plug-in information to complete the functions of deleting the network card and recovering the IP and the like of the corresponding network plug-in;
still further, the plug-in making module makes a Multus plug-in supporting multiple networks for acting based on the container network interface machine, and the plug-in making module specifically comprises a configuration generating module, a plug-in reading module and a plug-in application module:
a configuration generation module: generating a Multus configuration file by utilizing the initialization script;
a plug-in reading module: reading existing network plug-ins of a current container cloud cluster;
a plug-in application module: using the read first network plug-in as a default proxy plug-in;
and initializing a script by using a configuration generation module to generate a configuration file of Multus, wherein the file name is 00-Multus.
A network plug-in agent is manufactured based on a container network interface machine, a plurality of networks are supported, and the network plug-in agent is realized through a network plug-in agent mechanism, for example, multus is a network proxy plug-in; multus is a network plug-in written based on a container network interface standard, and can realize the cyclic calling of other network plug-ins, thereby generating a plurality of network cards for a container group.
Finally, it should be noted that: the above examples are only intended to illustrate the technical solution of the present invention, but not to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.
Claims (4)
1. A Kubernetes-based multi-network card container implementation method is characterized by comprising the following specific steps:
s1, reading and sequencing all container network plug-ins under a container network interface configuration catalog by using the network plug-ins;
s2, loading and checking the container network configuration file, defining by using a CNI standard format and using an expanded network plug-in as a default network plug-in of a container manager;
s3, acquiring the information of the default network plug-in, calling the default network plug-in to complete the IP distribution function:
s301, acquiring default network plug-ins and additional network plug-in information by reading comments of the container group;
s302, caching network plug-in information on the tape node;
s303, recursively calling an adding command of the proxy plug-in to complete network card generation and IP distribution functions of the network plug-in;
s304, returning an execution result to the network plug-in;
s4, a network plug-in supporting multiple networks is manufactured to act on the basis of the container network interface machine:
s401, generating a Multus configuration file by using an initialization script;
s402, reading existing network plug-ins of the current container cloud cluster;
s403 uses the read first network plug-in as a default proxy plug-in.
2. The method as claimed in claim 1, wherein said S303 completes the network card deletion and IP recycling function of the corresponding network card by reading the cached container proxy network card information and recursively invoking the delete command of the proxy card
3. A multi-network card container implementation system based on Kubernetes is characterized by specifically comprising a plug-in reading module, a plug-in definition module, a plug-in distribution module and a plug-in manufacturing module:
a plug-in reading module: reading all container network plug-ins in a container network interface configuration directory by using the network plug-ins and sequencing the container network plug-ins;
a plug-in definition module: loading and checking a container network configuration file, defining by using a CNI standard format and using an expanded network plug-in as a container manager default network plug-in;
a plug-in distribution module: acquiring information of a default network plug-in, and calling the default network plug-in to complete an IP distribution function;
the plug-in distribution module specifically comprises an information reading module, an information caching module, a function setting module and an execution returning module:
an information reading module: acquiring default network plug-ins and additional network plug-in information by reading comments of the container group;
the information caching module: caching network plug-in information on the tape node;
a function setting module: recursively calling an adding command of the proxy plug-in to realize the network card generation and IP distribution functions of the network plug-in;
an execution return module: returning an execution result to the network plug-in;
a plug-in manufacturing module: a network plug-in supporting multiple networks is manufactured to carry out proxy based on the container network interface machine;
the plug-in manufacturing module specifically comprises a configuration generation module, a plug-in reading module and a plug-in application module:
a configuration generation module: generating a Multus configuration file by utilizing the initialization script;
a plug-in reading module: reading an existing network plug-in of a current container cloud cluster;
a plug-in application module: and using the read first network plug-in as a default proxy plug-in.
4. The system as claimed in claim 3, wherein the function setting module recursively calls a delete command of the proxy plug-in by reading the cached container proxy network plug-in information to complete the network card deletion and IP recovery functions of the corresponding network plug-in.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011227634.2A CN112398936B (en) | 2020-11-06 | 2020-11-06 | Kubernetes-based multi-network card container implementation method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011227634.2A CN112398936B (en) | 2020-11-06 | 2020-11-06 | Kubernetes-based multi-network card container implementation method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112398936A CN112398936A (en) | 2021-02-23 |
| CN112398936B true CN112398936B (en) | 2023-03-28 |
Family
ID=74598223
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011227634.2A Active CN112398936B (en) | 2020-11-06 | 2020-11-06 | Kubernetes-based multi-network card container implementation method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112398936B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114500279B (en) * | 2021-12-30 | 2024-03-08 | 天翼云科技有限公司 | Plug-in configuration method and device |
| CN115314376B (en) * | 2022-08-01 | 2024-01-19 | 北京金山云网络技术有限公司 | Method and device for deploying network plug-ins in cluster, electronic equipment and storage medium |
| CN115314353B (en) * | 2022-08-10 | 2023-09-19 | 中电云数智科技有限公司 | Device and method for realizing single-pod multi-network card based on kubernetes |
| CN115913937B (en) * | 2023-01-09 | 2023-05-23 | 苏州浪潮智能科技有限公司 | Container multi-network card network configuration method, device, equipment and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2016188240A1 (en) * | 2016-01-07 | 2016-12-01 | 中兴通讯股份有限公司 | Method and device for configuring multiple network cards |
| CN106506314A (en) * | 2016-09-30 | 2017-03-15 | 北京赢点科技有限公司 | Network high availability method and device based on docker |
| CN110311948A (en) * | 2019-05-17 | 2019-10-08 | 北京瀚海星云科技有限公司 | Communication means between container/container group and the container cloud network system based on this |
| CN111371627A (en) * | 2020-03-24 | 2020-07-03 | 广西梯度科技有限公司 | Method for setting multiple IP (Internet protocol) in Pod in Kubernetes |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109039771B (en) * | 2018-09-04 | 2021-07-20 | 浪潮云信息技术股份公司 | Multi-network card binding configuration method and system |
| CN110138606B (en) * | 2019-05-06 | 2022-03-15 | 携程旅游信息技术（上海）有限公司 | Container network configuration method and system |
| CN110198364B (en) * | 2019-05-17 | 2021-09-14 | 深圳致星科技有限公司 | Container cloud distributed training data communication method based on designated DNS analysis |
| CN110737508A (en) * | 2019-10-14 | 2020-01-31 | 浪潮云信息技术有限公司 | cloud container service network system based on wave cloud and implementation method |
| CN111147297B (en) * | 2019-12-23 | 2022-07-15 | 广东省新一代通信与网络创新研究院 | Multi-layer network plane construction method of kubernets |
| CN111176788B (en) * | 2019-12-24 | 2023-08-25 | 优刻得科技股份有限公司 | Deployment method and system for main nodes of Kubernetes cluster |
-
2020
- 2020-11-06 CN CN202011227634.2A patent/CN112398936B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2016188240A1 (en) * | 2016-01-07 | 2016-12-01 | 中兴通讯股份有限公司 | Method and device for configuring multiple network cards |
| CN106506314A (en) * | 2016-09-30 | 2017-03-15 | 北京赢点科技有限公司 | Network high availability method and device based on docker |
| CN110311948A (en) * | 2019-05-17 | 2019-10-08 | 北京瀚海星云科技有限公司 | Communication means between container/container group and the container cloud network system based on this |
| CN111371627A (en) * | 2020-03-24 | 2020-07-03 | 广西梯度科技有限公司 | Method for setting multiple IP (Internet protocol) in Pod in Kubernetes |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112398936A (en) | 2021-02-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112398936B (en) | Kubernetes-based multi-network card container implementation method and system | |
| CN111857873A (en) | Method for realizing cloud native container network | |
| CN110019081A (en) | Data persistence processing method, device, system and readable storage medium storing program for executing | |
| JP7369860B2 (en) | Access docking component, system, and method and apparatus using the access docking component | |
| CN112040030B (en) | Message transmission method and device, computer equipment and storage medium | |
| CN111314450B (en) | Data transmission method and device, electronic equipment and computer storage medium | |
| CN111049876A (en) | Lightweight telecom cloud edge computing system architecture | |
| CN108089912A (en) | A kind of virtual machine surpasses emerging system construction method and device with container | |
| CN109714188A (en) | Configuration data management method, equipment and storage medium based on Zookeeper | |
| CN110389935A (en) | A kind of method, equipment and computer storage medium starting small routine | |
| US20240089328A1 (en) | Systems and methods for dynamic federated api generation | |
| CN105260377A (en) | Updating method and system based on hierarchical storage | |
| CN114650223B (en) | Network configuration method and device of Kubernetes cluster and electronic equipment | |
| CN114244654B (en) | URL forwarding method, device, equipment and computer storage medium | |
| CN110061857B (en) | Method and system for opening and sharing multiple MEC (Multi-media Engineer) capabilities | |
| CN112003794B (en) | Floating IP current limiting method, system, terminal and storage medium | |
| CN110795209B (en) | Control method and device | |
| CN111130978A (en) | Network traffic forwarding method and device, electronic equipment and machine-readable storage medium | |
| CN116032614A (en) | Container network micro-isolation method, device, equipment and medium | |
| CN106790521B (en) | System and method for distributed networking by using node equipment based on FTP | |
| CN107592340A (en) | The method and apparatus of remote operation management server | |
| CN115296995B (en) | Switch configuration method, device, electronic equipment and storage medium | |
| CN109068170A (en) | A kind of storage method, device, terminal and the storage medium of barrage message | |
| CN116155890B (en) | Method and device for realizing distributed file system | |
| CN114640646B (en) | System, device and method for binding container public network IP based on ARP proxy |
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 |