CN112702211A - Network service grid system based on Kubernetes - Google Patents
Network service grid system based on Kubernetes Download PDFInfo
- Publication number
- CN112702211A CN112702211A CN202011611246.4A CN202011611246A CN112702211A CN 112702211 A CN112702211 A CN 112702211A CN 202011611246 A CN202011611246 A CN 202011611246A CN 112702211 A CN112702211 A CN 112702211A
- Authority
- CN
- China
- Prior art keywords
- terminal
- network
- client
- network service
- manager
- 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
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/04—Network management architectures or arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
Abstract
The invention provides a network service grid system based on Kubernetes, which belongs to the field of Kubernetes network management systems in cloud computing technology and comprises a terminal, a client, a registry, a manager and a grid repeater; the terminal is responsible for providing network service for the outside, and is responsible for receiving a request from one or more clients and providing the network service for the clients; the client is a client which needs to use dynamic advanced network functions; a registry of related objects and components in the web services grid; the manager is a control component of the web services grid; mesh repeaters are data plane components that provide an end-to-end connection from a client to a network service endpoint. The invention can provide dynamic advanced network functions for applications deployed in Kubernets and complement short boards supported by the Kubernets on cloud native application networks.
Description
Technical Field
The invention relates to the field of Kubernets network management systems in cloud computing technology, in particular to a network service grid system based on Kubernets.
Background
With the continuous maturation of technologies in the fields of cloud computing and micro services, more and more traditional single applications are split into a large number of micro services and begin to go to the cloud, kubernets have become a de facto standard for deployment of cloud native applications, micro services are deployed on kubernets, so that a large amount of east-west network traffic among services is generated, and in order to meet the requirements of the east-west traffic among applications in a cluster, the kubernets adopt a flat three-layer network model, and the purpose of the network model is to process the east-west network traffic of pod in the same cluster, so that the design is very simple and clear, and the model is completely adequate for common IT and enterprise application scenarios. However, for telecommunications and some advanced enterprise network requirements, the kubernets network has some limitations, for example, the pod is fixed after being created, and cannot be updated dynamically, so that the dynamic network requirements of the application cannot be met. Furthermore, Kubernetes' network is primarily directed to intra-cluster traffic, lacking support for cross-cloud and cross-cluster connectivity.
Disclosure of Invention
In order to solve the technical problems, the invention provides a network service grid system based on Kubernetes, which aims to provide some advanced network function services for applications deployed in the Kubernetes and complement short boards supported by the Kubernetes on cloud native application networks. By deploying various terminals for providing advanced network services, the application can be automatically connected to the terminal only by combining simple and easy-to-use yaml statement configuration, various advanced network functions are obtained, and different network requirements of the application are dynamically met.
The technical scheme of the invention is as follows:
a network service grid system based on Kubernetes is composed of terminal, client end, register table, manager and grid repeater
Wherein the content of the first and second substances,
the terminal is responsible for providing network service for the outside, and is responsible for receiving a request from one or more clients and providing the network service for the clients;
the client is a client which needs to use dynamic advanced network functions;
the registry of related objects and components in the network service grid comprises example information of network service terminals and managers;
the manager is a control component of the web services grid;
mesh repeaters are data plane components that provide an end-to-end connection from a client to a network service endpoint.
Further, in the above-mentioned case,
the managers are deployed on each node in the cluster, the managers on different nodes can communicate and negotiate with each other to form a distributed control plane, and the intercommunicated managers form a grid for connecting terminals and clients.
The manager is primarily responsible for two things:
1) processing a network service use request from a client, matching a network service terminal meeting the requirement for the request, and establishing a virtual connection to the network service terminal for the client;
2) and registering the network service terminal on the node where the network service terminal is located on the registry.
Further, in the above-mentioned case,
the mesh forwarder directly configures forwarding rules of the linux kernel, and can also be a network control plane of a third party.
The grid repeater is responsible for building a virtual point-to-point link between two newly-created network interfaces of the network service terminal and the client, the link can be regarded as a virtual network line between the two network interfaces, and data entering from one section can come out from the other end, so that the network connectivity from the client to the terminal is ensured.
Further, in the above-mentioned case,
the manager of the node where the terminal which is responsible for providing the network service is located is responsible for registering the node into the registry, and the Init Container in the client application Pod initiates a request for using the network service to the manager on the same node according to yaml; the manager may then query the registry for available network service terminals. The terminal may be located on the same node as the client or on a different node.
If the terminal is on the same node, the manager can communicate with the manager on the node where the terminal is located, the request is forwarded, the request connection is initiated, the terminal judges according to the service logic of the terminal, and if the service request of the client can be received, the connection request is received; and the manager of the node where the terminal is located calls the grid repeater to create a network interface, and the network interface is added into the Pod of the terminal.
If the terminal and the client are on different nodes, the manager of the node where the terminal is located informs the manager of the node where the client is located to receive the service request; and the manager of the node where the client is located calls the grid forwarder to create a network interface, adds the network interface into the client application Pod, performs corresponding network configuration and ensures that the network to the terminal is accessed.
The network service grid design based on Kubernetes can provide dynamic advanced network functions for applications deployed in the Kubernetes, also supports virtual machines and servers, is a cloud native network solution across cloud platforms, and accordingly complements the short board supported by the Kubernetes on the cloud native application network.
The invention has the advantages that
The method is simple and easy to use, and the client can use the advanced network services only through the Yaml statement.
The connection, IP address, subnet, route and the like between the client and the network service terminal do not need to be manually configured, the business logic details are processed by the network service grid framework, and the client is not aware.
The method is flexible and configurable, new network service types can be added into the network service grid according to requirements, and the network services can be realized and provided by a third party.
The number of the network service terminals can be horizontally expanded according to the workload, and the stability of the service is ensured.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer and more complete, the technical solutions in the embodiments of the present invention will be described below, it is obvious that the described embodiments are a part of the embodiments of the present invention, but not all embodiments, and all other embodiments obtained by a person of ordinary skill in the art without creative efforts based on the embodiments of the present invention belong to the protection scope of the present invention.
The invention provides a network service grid design based on Kubernetes, the core of the design consists of five parts, including a terminal, a client, a registry, a manager and a grid repeater. The network service grid provides a declarative way of yaml to provide network services for clients, and injects an Init Container into a client Pod which needs to use the network services through an adaptation webhook function of kubernets, and the Init Container is responsible for requesting the corresponding network services from the manager according to the yaml declaration file, so that an application program does not need to pay attention to the request of the network services and the connection creation process.
Further description is as follows:
terminal (I)
The terminal is responsible for providing network services for the outside, and is responsible for receiving requests from one or more clients and providing the network services for the clients.
(II) client
A client using a dynamic advanced network function is required.
(III) registry
The registry of related objects and components in the network service grid contains instance information of the network service terminals and managers.
(IV) manager
The managers are control components of the network service grid, are deployed on each node in the cluster, the managers on different nodes can communicate and negotiate with each other to form a distributed control plane, the managers which communicate with each other form a grid for connecting terminals and clients, and the managers are mainly responsible for two things:
1) the method comprises the steps of processing a network service use request from a client, matching a network service terminal meeting requirements for the request, and creating a virtual connection to the network service terminal for the client.
2) And registering the network service terminal on the node where the network service terminal is located on the registry.
(V) mesh repeater
The mesh forwarder is a data plane component providing end-to-end connection from a client to a network service terminal, and can directly configure forwarding rules of a linux kernel or can be a network control plane of a third party. The method is used for building a virtual point-to-point link between two newly-created network interfaces of a network service terminal and a client, the link can be regarded as a virtual network line between the two network interfaces, and data entering from one section can come out from the other end, so that the network connectivity from the client to the terminal is ensured.
Firstly, a terminal responsible for providing network service is required, a manager of a node where the terminal is located is responsible for registering the terminal in a registry, and an Init Container in a client application Pod initiates a request for using the network service to the manager on the same node according to yaml. Then the manager will inquire the available network service terminal to the registry, the terminal may be located on the same node as the client or on different node, if on different node, the manager will communicate with the manager on the node where the terminal is located, forward the request, initiate the request connection, the terminal makes the judgment according to its own business logic, if can accept the service request of the client, then accept the connection request. And the manager of the node where the terminal is located calls the grid repeater to create a network interface, and the network interface is added into the Pod of the terminal. If the terminal and the client are on different nodes, the manager of the node where the terminal is located informs the manager of the node where the client is located to receive the service request. And the manager of the node where the client is located calls the grid forwarder to create a network interface, adds the network interface into the client application Pod, performs corresponding network configuration and ensures that the network to the terminal is accessed.
The invention is based on the declaration type yaml configuration of Kubernets, and can provide high-level network service for the application deployed in the Kubernets by combining with a network service terminal.
The network connection from the client to the network service terminal is automatically opened through the yaml configuration, the availability of the network service is ensured, and the manual configuration of the client is not needed.
The new network service type can be added into the network service grid according to the requirement, and the requirements of different clients on various high-level network services are met.
The number of terminals providing network services can be horizontally expanded according to the workload, and the availability and stability of the services are ensured.
The above description is only a preferred embodiment of the present invention, and is only used to illustrate the technical solutions of the present invention, and not to limit the protection scope of the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention shall fall within the protection scope of the present invention.
Claims (9)
1. A network service grid system based on Kubernetes is characterized in that,
includes terminal, client end, register table, manager and grid repeater
Wherein the content of the first and second substances,
the terminal is responsible for providing network service for the outside, and is responsible for receiving a request from one or more clients and providing the network service for the clients;
the client is a client which needs to use dynamic advanced network functions;
the registry of related objects and components in the network service grid comprises example information of network service terminals and managers;
the manager is a control component of the web services grid;
mesh repeaters are data plane components that provide an end-to-end connection from a client to a network service endpoint.
2. The system of claim 1,
the managers are deployed on each node in the cluster, the managers on different nodes can communicate and negotiate with each other to form a distributed control plane, and the intercommunicated managers form a grid for connecting terminals and clients.
3. The system of claim 2,
the manager is primarily responsible for two things:
1) processing a network service use request from a client, matching a network service terminal meeting the requirement for the request, and establishing a virtual connection to the network service terminal for the client;
2) and registering the network service terminal on the node where the network service terminal is located on the registry.
4. The system of claim 2,
the mesh forwarder directly configures forwarding rules of the linux kernel, and can also be a network control plane of a third party.
5. The system of claim 2 or 4,
the grid repeater is responsible for building a virtual point-to-point link between two newly-created network interfaces of the network service terminal and the client, the link can be regarded as a virtual network line between the two network interfaces, and data entering from one section can come out from the other end, so that the network connectivity from the client to the terminal is ensured.
6. The system of claim 5,
the manager of the node where the terminal which is responsible for providing the network service is located is responsible for registering the node into the registry, and the Init Container in the client application Pod initiates a request for using the network service to the manager on the same node according to yaml; the manager may then query the registry for available network service terminals.
7. The system of claim 6,
the terminal may be located on the same node as the client or on a different node.
8. The system of claim 7,
if the terminal is on the same node, the manager can communicate with the manager on the node where the terminal is located, the request is forwarded, the request connection is initiated, the terminal judges according to the service logic of the terminal, and if the service request of the client can be received, the connection request is received; and the manager of the node where the terminal is located calls the grid repeater to create a network interface, and the network interface is added into the Pod of the terminal.
9. The system of claim 7,
if the terminal and the client are on different nodes, the manager of the node where the terminal is located informs the manager of the node where the client is located to receive the service request; and the manager of the node where the client is located calls the grid forwarder to create a network interface, adds the network interface into the client application Pod, performs corresponding network configuration and ensures that the network to the terminal is accessed.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011611246.4A CN112702211B (en) | 2020-12-30 | 2020-12-30 | Network service grid system based on Kubernetes |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011611246.4A CN112702211B (en) | 2020-12-30 | 2020-12-30 | Network service grid system based on Kubernetes |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112702211A true CN112702211A (en) | 2021-04-23 |
| CN112702211B CN112702211B (en) | 2022-06-24 |
Family
ID=75512564
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011611246.4A Active CN112702211B (en) | 2020-12-30 | 2020-12-30 | Network service grid system based on Kubernetes |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112702211B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117155939A (en) * | 2023-10-31 | 2023-12-01 | 北京比格大数据有限公司 | Method for realizing cross-cluster resource scheduling |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105282195A (en) * | 2014-06-27 | 2016-01-27 | 中兴通讯股份有限公司 | Network service providing, strategy rule evaluating and service component selecting method and device |
| CN106227611A (en) * | 2016-07-26 | 2016-12-14 | 北京北森云计算股份有限公司 | The dynamic micro services call method of a kind of multilingual cloud compiling and device |
| US20170111241A1 (en) * | 2015-10-19 | 2017-04-20 | Draios Inc. | Automated service-oriented performance management |
| CN108519911A (en) * | 2018-03-23 | 2018-09-11 | 上饶市中科院云计算中心大数据研究院 | The dispatching method and device of resource in a kind of cluster management system based on container |
| CN110198231A (en) * | 2018-05-08 | 2019-09-03 | 腾讯科技（深圳）有限公司 | Capacitor network management method and system and middleware for multi-tenant |
| US10484334B1 (en) * | 2013-02-26 | 2019-11-19 | Zentera Systems, Inc. | Distributed firewall security system that extends across different cloud computing networks |
| CN111026414A (en) * | 2019-12-12 | 2020-04-17 | 杭州安恒信息技术股份有限公司 | HDP platform deployment method based on kubernets |
| CN111371679A (en) * | 2020-03-09 | 2020-07-03 | 山东汇贸电子口岸有限公司 | Method for realizing API gateway based on kubernets and Kong |
| CN112035216A (en) * | 2020-09-01 | 2020-12-04 | 浪潮云信息技术股份公司 | Communication method for Kubernetes cluster network and OpenStack network |
-
2020
- 2020-12-30 CN CN202011611246.4A patent/CN112702211B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10484334B1 (en) * | 2013-02-26 | 2019-11-19 | Zentera Systems, Inc. | Distributed firewall security system that extends across different cloud computing networks |
| CN105282195A (en) * | 2014-06-27 | 2016-01-27 | 中兴通讯股份有限公司 | Network service providing, strategy rule evaluating and service component selecting method and device |
| US20170111241A1 (en) * | 2015-10-19 | 2017-04-20 | Draios Inc. | Automated service-oriented performance management |
| CN106227611A (en) * | 2016-07-26 | 2016-12-14 | 北京北森云计算股份有限公司 | The dynamic micro services call method of a kind of multilingual cloud compiling and device |
| CN108519911A (en) * | 2018-03-23 | 2018-09-11 | 上饶市中科院云计算中心大数据研究院 | The dispatching method and device of resource in a kind of cluster management system based on container |
| CN110198231A (en) * | 2018-05-08 | 2019-09-03 | 腾讯科技（深圳）有限公司 | Capacitor network management method and system and middleware for multi-tenant |
| CN111026414A (en) * | 2019-12-12 | 2020-04-17 | 杭州安恒信息技术股份有限公司 | HDP platform deployment method based on kubernets |
| CN111371679A (en) * | 2020-03-09 | 2020-07-03 | 山东汇贸电子口岸有限公司 | Method for realizing API gateway based on kubernets and Kong |
| CN112035216A (en) * | 2020-09-01 | 2020-12-04 | 浪潮云信息技术股份公司 | Communication method for Kubernetes cluster network and OpenStack network |
Non-Patent Citations (3)
| Title |
|---|
| 夏之斌等: "一种云计算的虚拟网络管理系统", 《软件》 * |
| 李翔: "在私有Kubernetes集群中实现服务的负载均衡", 《电子技术与软件工程》 * |
| 齐磊等: "基于容器技术的PaaS云平台方案", 《电信科学》 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117155939A (en) * | 2023-10-31 | 2023-12-01 | 北京比格大数据有限公司 | Method for realizing cross-cluster resource scheduling |
| CN117155939B (en) * | 2023-10-31 | 2024-02-27 | 北京比格大数据有限公司 | Method for realizing cross-cluster resource scheduling |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112702211B (en) | 2022-06-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111106991B (en) | Cloud special line system and service issuing and opening method thereof | |
| CN103780471B (en) | Multiple controller network device managing method applied to software defined network | |
| CN105450553A (en) | Mechanism for management controllers to learn the control plane hierarchy in a data center environment | |
| WO2019127418A1 (en) | Network service management method, related device and system | |
| US11665088B2 (en) | Assisted replication in software defined network | |
| CN110838964B (en) | Network docking system for virtual network and physical network | |
| CN104993998A (en) | Enterprise-level safety instant messaging system supporting cloud deploying and method | |
| CN108011732A (en) | Method, controller and the system of configuration service resource | |
| CN112769602B (en) | System and method for unified configuration management of white box switch and network operating system | |
| CN105939267B (en) | Outband management method and device | |
| CN112702211B (en) | Network service grid system based on Kubernetes | |
| US20220350637A1 (en) | Virtual machine deployment method and related apparatus | |
| US20190281478A1 (en) | Integrated Access System | |
| WO2021078058A1 (en) | Resource scheduling method, apparatus and device, and computer-readable storage medium | |
| CN104113791A (en) | Automatically switched optical network evolution system and method | |
| CN116074160A (en) | Virtual networking public network forwarding method for GPU rendering computing node cluster | |
| CN215010316U (en) | Double-stack three-network intercommunication platform system | |
| CN112910959B (en) | SDN-based network interconnection method for multiple Kubernetes clusters | |
| CN114979139A (en) | Management system and method of heterogeneous virtual gateway in edge computing scene | |
| CN114189485A (en) | Network port management method and system of switch and computer readable storage medium | |
| CN108111323A (en) | Realization system of igmpsnooping protocol under vxworks system | |
| CN114650290A (en) | Network connection method, processing device, terminal and storage medium | |
| CN207560021U (en) | A kind of Internet phone-calling quality improvement system based on dynamic Cloud Server | |
| CN114500646B (en) | Decentralizing ESB cloud platform system and service calling method thereof | |
| WO2023169124A1 (en) | Multi-station cascade system, calling method and related device |
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 |