CN115801733A - Network address allocation method and device, electronic equipment and readable medium - Google Patents
Network address allocation method and device, electronic equipment and readable medium Download PDFInfo
- Publication number
- CN115801733A CN115801733A CN202310052249.6A CN202310052249A CN115801733A CN 115801733 A CN115801733 A CN 115801733A CN 202310052249 A CN202310052249 A CN 202310052249A CN 115801733 A CN115801733 A CN 115801733A
- Authority
- CN
- China
- Prior art keywords
- network
- subnet
- network address
- container
- cluster
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 74
- 238000012790 confirmation Methods 0.000 claims abstract description 48
- 238000004891 communication Methods 0.000 claims description 18
- 238000004590 computer program Methods 0.000 claims description 6
- 238000012545 processing Methods 0.000 abstract description 2
- 238000010586 diagram Methods 0.000 description 8
- 230000008569 process Effects 0.000 description 5
- 230000009471 action Effects 0.000 description 3
- 230000009467 reduction Effects 0.000 description 3
- 230000000694 effects Effects 0.000 description 2
- 238000007726 management method Methods 0.000 description 2
- 238000013500 data storage Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000007257 malfunction Effects 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 238000003672 processing method Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Images
Abstract
The embodiment of the invention provides a network address allocation method, a device, electronic equipment and a readable medium.A container network interface plug-in of a K8S cluster sends a subnet application request to a virtual network control plane of IaaS, acquires configuration confirmation information including at least one network address of a subnet returned by the virtual network control plane of the IaaS, and allocates an idle network address in the subnet to the container cluster when receiving a network address acquisition request sent by the container cluster. By the method, the container network interface plug-in applies for a plurality of network addresses to the virtual network control plane of the IaaS at one time, manages, distributes and releases the network addresses, does not need to initiate a request to the virtual network control plane of the IaaS each time, can reduce the performance pressure of the virtual network control plane of the IaaS, thereby improving the stability of the virtual network control plane, and can reduce the bandwidth overhead and the resource overhead of a CPU (Central processing Unit), a memory, a database and the like by reducing the number of the requests.
Description
Technical Field
The present invention relates to the field of container network technologies, and in particular, to a network address allocation method, a network address allocation apparatus, an electronic device, and a computer-readable medium.
Background
In cloud computing, a K8S (K8S for short) container network deployed on infrastructure as a Service (IaaS) needs to apply for and release a virtual network address of each container cluster with a virtual network control plane of IaaS. In K8S, containers can be dynamically created and destroyed, particularly in some large-scale scenarios, such as updating of applications such as advertisements or recommendations, a container cluster serving as an application carrier needs to be updated correspondingly, that is, a new container cluster is reconstructed, so that a large number of network address acquisition and release requests are initiated to a virtual network control plane, for example, 5 container clusters are constructed in each of 10000 large-scale virtual machines, and in a unified re-reconstruction process, a single virtual network address acquisition and release request can reach up to 10 ten thousand request volumes instantaneously, which is a huge challenge for the virtual network control plane of IaaS, and even can cause a virtual network control plane of IaaS to malfunction, which seriously affects normal operation of the network.
In order to solve the above problems, the prior art adopts the following processing methods: one is to improve the performance of the virtual network control plane of IaaS, which is difficult to achieve in the industry, and due to the scale and the inherent global overall problem of the network, the challenge of improving the performance of the virtual network control plane of IaaS is huge; one is to cut and avoid a control surface, and the method reduces the request pressure and the expense on the virtual network control surface of IaaS by using a mode of reducing the registration of nodes to a load balancer, and the method needs to identify the relation between a target running program and the nodes to judge whether a newly added node needs to be added to the load balancer, so that when the target running program is partially deployed, the effect of reducing the request pressure and the expense on the virtual network control surface of IaaS can be achieved, but for the condition that the target running programs of all the nodes need to be deployed, the effect of reducing the pressure and the expense on the virtual network control surface of IaaS cannot be achieved; in addition, the constraint of the size of the K8S cluster is performed, but the limitation of the cluster size results in a limitation on the application scenario.
Disclosure of Invention
In view of the above problems, embodiments of the present invention are provided to provide a network address allocation method, a network address allocation apparatus, an electronic device, and a computer readable medium that overcome or at least partially solve the above problems.
The embodiment of the invention discloses a network address allocation method, which is applied to a K8S cluster, wherein the K8S cluster comprises a container network interface plug-in, and the container network interface plug-in is connected with a virtual network control plane of IaaS; the K8S cluster further comprises at least one container cluster, and the container network interface plug-in is used for allocating network addresses to the container cluster; the method comprises the following steps:
the container network interface plug-in sends a subnet application request to a virtual network control plane of the IaaS; the subnet application request carries network configuration information; the network configuration information comprises a main network number and a network address number of the subnet; the subnet is a private network applied to the K8S cluster;
receiving configuration confirmation information of the subnet, which is sent by a virtual network control plane of the IaaS; the configuration confirmation information records network addresses of the number of the network addresses in the subnet corresponding to the main network number;
when a network address acquisition request sent by the container cluster is received, distributing an idle network address in the subnet to the container cluster; the network address is used for providing an access address for an external device to access an application in the container cluster.
Optionally, the container network interface plug-in is configured with an unallocated list and an allocated list; the unallocated list is used for recording unallocated network addresses in the network addresses of the subnets; the allocated list is used for recording the allocated network addresses in the network addresses of the sub-networks;
when a network address acquisition request sent by the container cluster is received, allocating an idle network address in the subnet to the container cluster, including:
when a network address acquisition request sent by the container cluster is received, judging whether the network address exists in the unallocated list or not;
if the network address exists in the unallocated list, determining the network address at the head of the unallocated list as a target network address;
assigning the target network address to the cluster of containers.
Optionally, after the step of allocating an idle network address in the subnet to the container cluster when receiving the network address obtaining request sent by the container cluster, the method further includes:
deleting the target network address in the unallocated list and recording the target network address in the allocated list.
Optionally, after the step of receiving the configuration confirmation information of the subnet sent by the virtual network control plane of IaaS, the method further includes:
creating an unallocated list and an allocated list;
adding a network address of the number of network addresses of the subnet to the unallocated list.
Optionally, after the step of allocating an idle network address in the subnet to the container cluster when receiving a network address obtaining request sent by the container cluster, the method further includes:
receiving a network address release request sent by the container cluster; the network address release request is recorded with the target network address;
judging whether the target network address exists in the distributed list or not;
and if the target network address exists, deleting the target network address in the allocated list and recording the target network address at the tail part of the unallocated list.
The embodiment of the invention discloses a subnet allocation method, which is applied to a virtual network control plane of IaaS (infrastructure as a service), wherein a network managed by the virtual network control plane of the IaaS comprises at least one subnet, and the subnet is configured with at least one network address; the virtual network control plane of the IaaS is connected with a container network interface plug-in of a K8S cluster, the K8S cluster further comprises at least one container cluster, and the container cluster is connected with the container network interface plug-in; the method comprises the following steps:
receiving a subnet application request sent by the container network interface plug-in; the subnet application request carries network configuration information; the network configuration information comprises a main network number and a network address number of the subnet; the subnet is a private network applied to the K8S cluster;
sending the configuration confirmation information of the subnet to the container network interface plug-in; the configuration confirmation information records the network addresses of the number of the network addresses in the subnet corresponding to the main network number; the container network interface plug-in is used for managing the network address in the subnet and distributing the network address to the container cluster when receiving a network address acquisition request sent by the container cluster; the network address is used for providing an access address for an external device to access an application in the container cluster.
Optionally, after the step of sending the configuration confirmation information of the subnet to the container network interface plug-in, the method further includes:
and marking the network addresses of the network address number in the virtual network control plane of the IaaS as allocated states.
The embodiment of the invention discloses a network address allocation device, which is applied to a K8S cluster, wherein the K8S cluster comprises a container network interface plug-in, and the container network interface plug-in is connected with a virtual network control plane of IaaS; the K8S cluster further comprises at least one container cluster, and the container network interface plug-in is used for allocating network addresses to the container cluster; the device comprises:
a first sending module, configured to send, by the container network interface plug-in, a subnet application request to a virtual network control plane of the IaaS; the subnet application request carries network configuration information; the network configuration information comprises a main network number and a network address number of the subnet; the subnet is a private network applied to the K8S cluster;
a first receiving module, configured to receive configuration confirmation information of the subnet sent by the virtual network control plane of IaaS; the configuration confirmation information records the network addresses of the number of the network addresses in the subnet corresponding to the main network number;
the distribution module is used for distributing idle network addresses in the sub-network to the container cluster when receiving a network address acquisition request sent by the container cluster; the network address is used for providing an access address for an external device to access an application in the container cluster.
Optionally, the container network interface plug-in is configured with an unallocated list and an allocated list; the unallocated list is used for recording unallocated network addresses in the network addresses of the subnets; the allocated list is used for recording the allocated network addresses in the network addresses of the sub-networks;
the distribution module comprises:
the judging submodule is used for judging whether the network address exists in the unallocated list or not when a network address acquiring request sent by the container cluster is received;
a target network address determination submodule, configured to determine the network address at the head of the unallocated list as a target network address if the network address exists in the unallocated list;
an assignment submodule configured to assign the target network address to the container cluster.
Optionally, the apparatus further comprises:
a first update module to delete the target network address in the unallocated list and to record the target network address in the allocated list.
Optionally, the apparatus further comprises:
a creation module for creating an unallocated list and an allocated list;
an adding module to add network addresses of the number of network addresses of the subnet to the unallocated list.
Optionally, the apparatus further comprises:
a second receiving module, configured to receive a network address release request sent by the container cluster; the network address release request is recorded with the target network address;
a judging module, configured to judge whether the target network address exists in the allocated list;
and the second updating module is used for deleting the target network address in the allocated list and recording the target network address at the tail part of the unallocated list if the target network address exists.
The embodiment of the invention discloses a subnet distribution device, which is applied to a virtual network control plane of IaaS (infrastructure as a service), wherein a network managed by the virtual network control plane of the IaaS comprises at least one subnet, and the subnet is configured with at least one network address; the virtual network control plane of the IaaS is connected with a container network interface plug-in of a K8S cluster, the K8S cluster further comprises at least one container cluster, and the container cluster is connected with the container network interface plug-in; the device comprises:
a third receiving module, configured to receive a subnet application request sent by the container network interface plugin; the subnet application request carries network configuration information; the network configuration information comprises a main network number and a network address number of the subnet; the subnet is a private network applied to the K8S cluster;
the second sending module is used for sending the configuration confirmation information of the subnet to the container network interface plug-in; the configuration confirmation information records the network addresses of the number of the network addresses in the subnet corresponding to the main network number; the container network interface plug-in is used for managing the network address in the subnet and distributing the network address to the container cluster when receiving a network address acquisition request sent by the container cluster; the network address is used for providing an access address for an external device to access an application in the container cluster.
Optionally, the apparatus further comprises:
a marking module, configured to mark the network address of the network address amount in the virtual network control plane of IaaS as an allocated state.
The embodiment of the invention also discloses electronic equipment which comprises a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory finish mutual communication through the communication bus;
the memory is used for storing a computer program;
the processor is configured to implement the method according to the embodiment of the present invention when executing the program stored in the memory.
Embodiments of the invention also disclose one or more computer-readable media having instructions stored thereon, which, when executed by one or more processors, cause the processors to perform a method according to embodiments of the invention.
The embodiment of the invention has the following advantages:
in the embodiment of the invention, a container network interface plug-in of a K8S cluster sends a subnet application request to a virtual network control plane of IaaS, acquires configuration confirmation information including at least one network address of a subnet returned by the virtual network control plane of IaaS, and allocates an idle network address in the subnet to the container cluster when receiving a network address acquisition request sent by the container cluster. By the method, the container network interface plug-in applies at least one network address to the virtual network control surface of the IaaS at one time and manages the network addresses, so that the managed network addresses can be adopted to be distributed to the container cluster when the container cluster applies for the network addresses, a request does not need to be sent to the virtual network control surface of the IaaS every time as in the prior art, the request does not need to be sent to the virtual network control surface of the IaaS, the performance pressure of the virtual network control surface of the IaaS can be reduced, the stability of the virtual network control surface is improved, and the reduction of the number of the requests can reduce bandwidth overhead and resource overhead of a CPU, a memory, a database and the like.
Drawings
FIG. 1 is a system architecture diagram of a network address assignment provided in an embodiment of the present invention;
fig. 2 is a flowchart illustrating steps of a method for assigning network addresses according to an embodiment of the present invention;
FIG. 3 is a flow chart illustrating steps of another method for assigning network addresses provided in embodiments of the present invention;
fig. 4 is a flow chart of allocating and releasing network addresses provided in an embodiment of the present invention;
FIG. 5 is a flow chart illustrating steps of a method for subnet assignment provided in an embodiment of the present invention;
fig. 6 is a block diagram of a network address assignment device provided in an embodiment of the present invention;
fig. 7 is a block diagram of a subnet distribution device provided in an embodiment of the present invention;
fig. 8 is a block diagram of an electronic device provided in an embodiment of the invention;
fig. 9 is a schematic diagram of a computer-readable medium provided in an embodiment of the invention.
Detailed Description
In order to make the aforementioned objects, features and advantages of the present invention more comprehensible, the present invention is described in detail with reference to the accompanying drawings and the detailed description thereof.
In the prior art, each time a container network interface plug-in receives a network address acquisition request of a container cluster, the container network interface plug-in needs to acquire a network address from a virtual network control plane of the IaaS and then allocate the network address to the container cluster, and the virtual network control plane of the IaaS is crashed under the condition of a large amount of requests.
Referring to fig. 1, a system architecture diagram of network address assignment provided in an embodiment of the present invention is shown.
The K8S cluster 101 includes a container network interface plug-in 102 and at least one container cluster 103, and the container network interface plug-in 102 may be connected to a virtual network control plane 104 of IaaS and the container cluster 103, respectively.
The virtual network control plane 104 of IaaS is used to manage a public network, the public network of the virtual network control plane management 104 of IaaS may be provided for use by at least one K8S cluster 101, and the public network of the virtual network control plane management 104 of IaaS may be divided into at least one subnet, each subnet comprising at least one network address, so as to be assigned with a network address specific to the subnet of the K8S cluster 101 upon application by the container network interface plug-in 102 of the K8S cluster 101.
The container network interface plug-in 102 may apply for network addresses to the virtual network control plane 104 of IaaS, manage the applied network addresses, and assign network addresses to the container cluster 103.
The container cluster 103 may apply for a network address from the container network interface plug-in 102 and use the network address to provide an access address for an external device to access an application in the container cluster.
Referring to fig. 2, a flowchart illustrating steps of a network address allocation method provided in the embodiment of the present invention is shown, which specifically includes the following steps:
step 201, the container network interface plug-in sends a subnet application request to the virtual network control plane of IaaS; the subnet application request carries network configuration information; the network configuration information comprises a main network number and a network address number of the subnet; the subnet is a private network applied to the K8S cluster;
under the condition that a user needs to apply for a batch of network addresses for a certain K8S cluster, a container network interface plug-in of the K8S cluster can send a subnet application request carrying a network configuration message to a virtual network control plane of IaaS so as to obtain a batch of network addresses specially applied to the K8S cluster. The network configuration information may include a master network number and a network address number of the subnet, and the master network number and the network address number may be set for a user according to actual requirements. The primary network number may be used as a network prefix of each network address in the subnet, i.e. network addresses belonging to the same subnet have the same network prefix, for example, the network configuration message may include 128.14.35.7/20, and 128.14.35.7 is a network prefix.
Specifically, the container network interface plug-in may generate a network configuration message based on a main network number and a number of network addresses set by a user, generate a subnet application request by using the network configuration message, and send the subnet application request to a virtual network control plane of IaaS, so as to obtain a batch of network addresses.
After receiving the subnet application request, the virtual network control plane of IaaS can perform legal verification on the subnet application request, and can determine whether the subnet application request is legal by judging whether the number of the network addresses applied is within the peak range of the number of the network addresses of the subnet. The network address number peak range may be the number of unassigned network addresses in the network address of each subnet. If the number of the network addresses applied is within the peak value range of the number of the network addresses of the subnet, determining that the subnet application request is legal; and if the number of the network addresses applied is not in the peak range of the number of the network addresses of the subnet, determining that the subnet application request is illegal.
Under the condition that the subnet application request is determined to be legal, the virtual network control plane of the IaaS can determine a target subnet according to the main network number carried by the subnet application request, extract a corresponding number of network addresses from the network addresses of the subnet according to the number of the network addresses, issue the network addresses to the container network interface plug-in, and mark the issued network addresses in the virtual network control plane of the IaaS in an allocated state, so that the state of the virtual network control plane of the IaaS cannot be changed unless actively destroyed, and the virtual network control plane of the IaaS cannot accept the application and release of other K8S clusters to the network addresses.
the container network interface plug-in may receive a configuration confirmation message returned by the virtual network control plane of IaaS when sending the subnet application request to the virtual network control plane of IaaS, and the configuration confirmation message may record the network addresses of the number of network addresses in the subnet corresponding to the main network number. The container network interface plug-in may store and manage these network addresses upon receiving them.
Various types of applications, such as an advertisement application, a recommendation application, a game application, and the like, may be deployed in each container cluster, and an external device needs to access an application in the container cluster by accessing an access address, so that a network address may be allocated to each container cluster as the access address, so that the external device accesses the container cluster corresponding to the network address through the network address.
The K8S cluster can exist in a plurality of container clusters, and the network address allocated to one container cluster cannot be reallocated to other container clusters, so that the application of the container cluster corresponding to the network address is accessed by the external device through the specific network address, and therefore the container network interface plug-in can mark the allocated network address to distinguish which network addresses are allocated and which network addresses are unallocated. And may record to which container cluster each network address is assigned, e.g., may record the container cluster name, so that its corresponding network address may be released according to the container cluster name at a subsequent release.
Specifically, when receiving a network address acquisition request sent by a container cluster, the container network interface plug-in may first determine which network addresses are unallocated, extract one or more network addresses from the unallocated network addresses to allocate to the container cluster initiating the request, and record a container cluster message corresponding to the network address.
By the network address allocation method, the container network interface plug-in of the K8S cluster sends a subnet application request to the virtual network control plane of the IaaS, configuration confirmation information including at least one network address of the subnet returned by the virtual network control plane of the IaaS is obtained, and when a network address acquisition request sent by the container cluster is received, an idle network address in the subnet is allocated to the container cluster. By the method, the container network interface plug-in applies at least one network address to the virtual network control surface of the IaaS at one time and manages the network addresses, so that the managed network addresses can be adopted to be distributed to the container cluster when the container cluster applies for the network addresses, a request does not need to be sent to the virtual network control surface of the IaaS every time as in the prior art, the request does not need to be sent to the virtual network control surface of the IaaS, the performance pressure of the virtual network control surface of the IaaS can be reduced, the stability of the virtual network control surface is improved, and the reduction of the number of the requests can reduce bandwidth overhead and resource overhead of a CPU, a memory, a database and the like.
Referring to fig. 3, a flowchart illustrating steps of another network address assignment method provided in the embodiment of the present invention is shown, which may specifically include the following steps:
step 301, the container network interface plug-in sends a subnet application request to the virtual network control plane of IaaS; the subnet application request carries network configuration information; the network configuration information comprises a main network number and a network address number of the subnet; the subnet is a private network applied to the K8S cluster;
in an embodiment of the present invention, after the step of receiving configuration confirmation information of the subnet sent by the virtual network control plane of IaaS, the method further includes:
s11, creating an unallocated list and an allocated list;
in the embodiment of the present invention, the container network interface plug-in may manage the network addresses by setting an unallocated list and an allocated list, after receiving the network addresses sent by the virtual network control plane of IaaS.
In particular, the container network interface plug-in may create an unallocated list and an allocated list, record unallocated network addresses in the network addresses of the subnets using the unallocated list, and record allocated network addresses in the network addresses of the subnets using the allocated list.
S12, adding the network addresses of the number of the network addresses of the subnet into the unallocated list.
The unallocated list may be configured to record unallocated network addresses in the network addresses of the subnets, so that the container network interface plug-in may add the received network addresses of the number of network addresses of the subnets to the unallocated list after creating the unallocated list, so as to manage the unallocated network addresses.
in this embodiment of the present invention, the container network interface plug-in may be configured with an unallocated list and an allocated list, where the unallocated list may be used to record unallocated network addresses in the network addresses of the subnets, and the allocated list may be used to record allocated network addresses in the network addresses of the subnets.
Therefore, when receiving a network address acquisition request sent by a container cluster, the container network interface plug-in may first determine whether a network address exists in the unallocated list. If the unallocated list has a network address, the network address can be allocated to the container cluster; if the unallocated list does not have a network address, it may be determined that no idle network address exists in the network addresses managed by the container network interface plug-in, and the container cluster may be allocated.
upon determining that a network address exists in the unallocated list, the container network interface plug-in may extract the network address from the unallocated list for allocation to the container cluster. In particular, the container network interface plug-in may determine the network address at the head of the unallocated list as the target network address for allocation to the container cluster.
After determining the target network address, the container network interface plug-in may assign the target network address to the requesting container cluster and mark the target network address as assigned and the corresponding name of the requesting container cluster.
In an embodiment of the present invention, after the step of allocating a network address that is idle in the subnet to the container cluster when receiving a network address obtaining request sent by the container cluster, the method further includes:
s21, deleting the target network address in the unallocated list and recording the target network address in the allocated list.
The container network interface plug-in manages the network addresses applied from the virtual network control plane of IaaS, the unallocated network addresses can be used for being allocated to the newly-issued request container cluster, and the allocated network addresses cannot be allocated to other container clusters, so that the container network interface plug-in can manage the allocation state of the target network addresses after allocating the target network addresses to the issued request container cluster.
Specifically, the container network interface plug-in may delete the target network address from the unallocated list and record the target network address in the allocated list, thereby implementing the update of the allocation status of the target network address.
In an embodiment of the present invention, after the step of allocating an idle network address in the subnet to the container cluster when receiving a network address acquisition request sent by the container cluster, the method further includes:
s31, receiving a network address release request sent by the container cluster; the network address release request is recorded with the target network address;
the container cluster may send a network address release request to the container network interface plug-in describing the target network address in case the target network address is not needed, so that the container network interface plug-in recovers the target network address.
After receiving a network address release request sent by a container cluster, a container network interface plug-in can release a target network address recorded in the network address release request, so that the target network address can recover an unallocated state and is used for being allocated to other container clusters.
S32, judging whether the target network address exists in the distributed list or not;
the target network address may not be successfully added to the allocated list by the container network interface plug-in, and at this time, the allocated list may not record the target network address, so that the container network interface plug-in may first determine whether the target network address exists in the allocated list after receiving the network address release request. If so, the container network interface plug-in can update the distribution state of the target network address; if the target network address exists, the container network interface plug-in does not need to update the allocation state of the target network address, and can return a feedback message that the target network address is not found in the allocated list to the container cluster.
And S33, if the target network address exists, deleting the target network address in the allocated list and recording the target network address at the tail part of the unallocated list.
Upon determining that the target network address exists in the allocated list, the container network interface plug-in may update the allocation status of the target network address. Specifically, the container network interface plug-in may delete the target network address from the allocated list, and record the target network address at the tail of the unallocated list, thereby implementing the update of the allocation status of the target network address.
Referring to fig. 4, a flowchart of allocating and releasing a network address provided in an embodiment of the present invention is shown.
1. The method comprises the steps that a container network interface plug-in sends a subnet application request aiming at a batch of network addresses to a virtual network control plane of IaaS;
2. the virtual network control of IaaS returns at least one network address corresponding to the subnet application request to the container network interface plug-in; the container network interface plug-in manages the storage and allocation of these network addresses;
3. the container cluster which belongs to the same K8S cluster with the container network interface plug-in sends a network address acquisition request to the container network interface plug-in;
4. when receiving a network address acquisition request sent by a container cluster, a container network interface plug-in allocates a target network address to the container cluster by adopting the managed network addresses;
5. the container cluster sends a network address release request to the container network interface plug-in;
6. when receiving a network address release request sent by a container cluster, a container network interface plug-in releases a target network address corresponding to the network address release request and returns an execution confirmation message to the container cluster;
7. the container network interface plug-in can send subnet release requests aiming at the network addresses to a virtual network control plane of the IaaS under the condition that the network addresses are not needed;
8. and the virtual network control plane of the IaaS releases the network addresses corresponding to the subnet release request and returns an execution confirmation message to the container network interface plug-in.
According to the network address allocation method provided by the embodiment of the invention, the container network interface plug-in of the K8S cluster sends the subnet application request to the virtual network control plane of the IaaS, the configuration confirmation information including at least one network address of the subnet returned by the virtual network control plane of the IaaS is obtained, and when the network address acquisition request sent by the container cluster is received, the idle network address in the subnet is allocated to the container cluster. By the method, the container network interface plug-in applies at least one network address to the virtual network control surface of the IaaS at one time and manages the network addresses, so that the managed network addresses can be adopted to be distributed to the container cluster when the container cluster applies for the network addresses, a request does not need to be sent to the virtual network control surface of the IaaS every time as in the prior art, the request does not need to be sent to the virtual network control surface of the IaaS, the performance pressure of the virtual network control surface of the IaaS can be reduced, the stability of the virtual network control surface is improved, and the reduction of the number of the requests can reduce bandwidth overhead and resource overhead of a CPU, a memory, a database and the like.
Referring to fig. 5, a flowchart illustrating steps of a subnet allocation method provided in an embodiment of the present invention is shown, which may specifically include the following steps:
step 501, receiving a subnet application request sent by the container network interface plug-in; the subnet application request carries network configuration information; the network configuration information comprises a main network number and a network address number of the subnet; the subnet is a private network applied to the K8S cluster;
in the embodiment of the present invention, the virtual network control plane of IaaS is used to manage a network, and the network managed by the virtual network control plane of IaaS may be divided into at least one subnet, where each subnet includes at least one network address, so as to allocate a network address dedicated to the subnet of the K8S cluster to the container network interface plug-in 102 of the K8S cluster 101 when applying for the application.
When a user needs to apply for a batch of network addresses for a certain K8S cluster, a container network interface plug-in of the K8S cluster may send a subnet application request to a virtual network control plane of IaaS to obtain a batch of network addresses specially applied to the K8S cluster.
Therefore, the virtual network control plane of IaaS can receive a subnet application request carrying a network configuration message sent by a receiving container network interface plug-in, where the network configuration information may include a main network number and a network address number of a subnet, and the main network number and the network address number may be set for a user according to actual requirements. The primary network number may be used as a network prefix of each network address in the subnet, i.e. network addresses belonging to the same subnet have the same network prefix, for example, the network configuration message may include 128.14.35.7/20, and 128.14.35.7 is a network prefix.
Step 502, sending configuration confirmation information of the subnet to the container network interface plug-in; the configuration confirmation information records the network addresses of the number of the network addresses in the subnet corresponding to the main network number; the container network interface plug-in is used for managing the network address in the subnet and distributing the network address to the container cluster when receiving a network address acquisition request sent by the container cluster; the network address is used for providing an access address for an external device to access an application in the container cluster.
After receiving the subnet application request, the virtual network control plane of IaaS can legally verify the subnet application request, and can determine whether the subnet application request is legal by judging whether the number of the network addresses applied is within the peak range of the number of the network addresses of the subnet. The peak range of network address numbers may be the number of unassigned network addresses in the network address of each subnet. If the number of the network addresses applied is within the peak value range of the number of the network addresses of the subnet, determining that the subnet application request is legal; and if the number of the network addresses applied is not in the peak range of the number of the network addresses of the subnet, determining that the subnet application request is illegal.
Under the condition that the subnet application request is determined to be legal, the virtual network control plane of the IaaS can determine a target subnet according to the main network number carried by the subnet application request, extract a corresponding number of network addresses from the network addresses of the subnet according to the number of the network addresses, generate configuration confirmation messages by adopting the network addresses and send the configuration confirmation messages to the container network interface plug-in. The container network interface plug-in may store and manage these network addresses after receiving these network addresses included in the configuration confirmation message.
In an embodiment of the present invention, after the step of sending the configuration confirmation information of the subnet to the container network interface plug-in, the method further includes:
and marking the network addresses of the network address number in the virtual network control plane of the IaaS as allocated states.
After the virtual network control plane of IaaS sends the configuration confirmation message containing the network address to the container network interface plug-in, the issued network addresses in the virtual network control plane of IaaS can be marked as allocated states, so that the states of the virtual network control plane of IaaS cannot be changed unless actively destroyed, the virtual network control plane of IaaS cannot accept application and release of other K8S clusters to the network addresses, and each network address is guaranteed to be used by a unique K8S cluster before being recovered.
By the network address allocation method provided by the embodiment of the invention, the virtual network control plane of IaaS receives the subnet application request sent by the container network interface plug-in, and sends configuration confirmation information containing the network addresses of a batch of subnets to the container network interface plug-in. By the method, after receiving the subnet application request sent by the container network interface plug-in, the virtual network control plane of the IaaS can issue at least one network address corresponding to the subnet application request to the container network interface plug-in at one time, so that the container network interface plug-in can manage a batch of network addresses, and the managed network addresses can be adopted to be distributed to the container cluster when the container cluster applies for the network addresses, and the method does not need to send the request to the virtual network control plane of the IaaS every time as in the prior art, does not need to initiate the request to the virtual network control plane of the IaaS, can reduce the performance pressure of the virtual network control plane of the IaaS, and further improves the stability of the virtual network control plane.
It should be noted that, for simplicity of description, the method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present invention is not limited by the illustrated order of acts, as some steps may occur in other orders or concurrently in accordance with the embodiments of the present invention. Further, those of skill in the art will appreciate that the embodiments described in the specification are presently preferred and that no particular act is required to implement the embodiments of the invention.
Referring to fig. 6, a block diagram of a network address allocating apparatus provided in the embodiment of the present invention is shown, and specifically, the apparatus may include the following modules:
a first sending module 601, configured to send a subnet application request to a virtual network control plane of the IaaS by the container network interface plugin; the subnet application request carries network configuration information; the network configuration information comprises a main network number and a network address number of the subnet; the subnet is a private network applied to the K8S cluster;
a first receiving module 602, configured to receive configuration confirmation information of the subnet, which is sent by the virtual network control plane of IaaS; the configuration confirmation information records the network addresses of the number of the network addresses in the subnet corresponding to the main network number;
an allocating module 603, configured to allocate, when receiving a network address acquisition request sent by the container cluster, an idle network address in the subnet to the container cluster; the network address is used for providing an access address for an external device to access an application in the container cluster.
Optionally, the container network interface plug-in is configured with an unallocated list and an allocated list; the unallocated list is used for recording unallocated network addresses in the network addresses of the subnets; the allocated list is used for recording the allocated network addresses in the network addresses of the sub-networks;
the allocating module 603 includes:
the judging submodule is used for judging whether the network address exists in the unallocated list or not when a network address acquiring request sent by the container cluster is received;
a target network address determining submodule, configured to determine, if the network address exists in the unallocated list, the network address at the head of the unallocated list as a target network address;
an assignment submodule for assigning the target network address to the container cluster.
Optionally, the apparatus further comprises:
a first update module to delete the target network address in the unassigned list and record the target network address in the assigned list.
Optionally, the apparatus further comprises:
the creation module is used for creating an unallocated list and an allocated list;
an adding module for adding the network addresses of the number of network addresses of the subnet to the unassigned list.
Optionally, the apparatus further comprises:
a second receiving module, configured to receive a network address release request sent by the container cluster; the network address release request is recorded with the target network address;
a judging module, configured to judge whether the target network address exists in the allocated list;
and the second updating module is used for deleting the target network address in the allocated list and recording the target network address at the tail part of the unallocated list if the target network address exists.
Referring to fig. 7, a block diagram of a structure of a subnet distribution device provided in the embodiment of the present invention is shown, which may specifically include the following modules:
a third receiving module 701, configured to receive a subnet application request sent by the container network interface plug-in; the subnet application request carries network configuration information; the network configuration information comprises a main network number and a network address number of the subnet; the subnet is a private network applied to the K8S cluster;
a second sending module 702, configured to send configuration confirmation information of the subnet to the container network interface plug-in; the configuration confirmation information records network addresses of the number of the network addresses in the subnet corresponding to the main network number; the container network interface plug-in is used for managing the network address in the subnet and distributing the network address to the container cluster when receiving a network address acquisition request sent by the container cluster; the network address is used for providing an access address for an external device to access an application in the container cluster.
Optionally, the apparatus further comprises:
a marking module, configured to mark the network address of the network address number in the virtual network control plane of IaaS as an allocated state.
For the device embodiment, since it is basically similar to the method embodiment, the description is simple, and for the relevant points, refer to the partial description of the method embodiment.
In addition, an electronic device is further provided in an embodiment of the present invention, as shown in fig. 8, and includes a processor 801, a communication interface 802, a memory 803, and a communication bus 804, where the processor 801, the communication interface 802, and the memory 803 complete mutual communication through the communication bus 804,
a memory 803 for storing a computer program;
the processor 801 is configured to implement the following steps when executing the program stored in the memory 803:
the container network interface plug-in sends a subnet application request to a virtual network control plane of the IaaS; the subnet application request carries network configuration information; the network configuration information comprises a main network number and a network address number of the subnet; the subnet is a private network applied to the K8S cluster;
receiving configuration confirmation information of the subnet, which is sent by a virtual network control plane of the IaaS; the configuration confirmation information records network addresses of the number of the network addresses in the subnet corresponding to the main network number;
when a network address acquisition request sent by the container cluster is received, distributing an idle network address in the subnet to the container cluster; the network address is used for providing an access address for an external device to access an application in the container cluster.
Optionally, the container network interface plug-in is configured with an unallocated list and an allocated list; the unallocated list is used for recording unallocated network addresses in the network addresses of the subnet; the allocated list is used for recording the allocated network addresses in the network addresses of the sub-networks;
when a network address acquisition request sent by the container cluster is received, allocating an idle network address in the subnet to the container cluster, including:
when a network address acquisition request sent by the container cluster is received, judging whether the network address exists in the unallocated list or not;
if the network address exists in the unallocated list, determining the network address at the head of the unallocated list as a target network address;
assigning the target network address to the cluster of containers.
Optionally, after the step of allocating an idle network address in the subnet to the container cluster when receiving a network address obtaining request sent by the container cluster, the method further includes:
deleting the target network address in the unallocated list and recording the target network address in the allocated list.
Optionally, after the step of receiving the configuration confirmation information of the subnet sent by the virtual network control plane of IaaS, the method further includes:
creating an unallocated list and an allocated list;
adding a network address of the number of network addresses of the subnet to the unassigned list.
Optionally, after the step of allocating an idle network address in the subnet to the container cluster when receiving the network address obtaining request sent by the container cluster, the method further includes:
receiving a network address release request sent by the container cluster; the network address release request is recorded with the target network address;
judging whether the target network address exists in the distributed list or not;
and if the target network address exists, deleting the target network address in the allocated list and recording the target network address at the tail part of the unallocated list.
The communication bus mentioned in the above terminal may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The communication bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown, but this does not mean that there is only one bus or one type of bus.
The communication interface is used for communication between the terminal and other equipment.
The memory may include a Random Access Memory (RAM) or a non-volatile memory (non-volatile memory), such as at least one disk memory. Optionally, the memory may also be at least one memory device located remotely from the processor.
The processor may be a general-purpose processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; the Integrated Circuit may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, a discrete Gate or transistor logic device, or a discrete hardware component.
As shown in fig. 9, in a further embodiment provided by the present invention, a computer-readable storage medium 901 is further provided, which has instructions stored therein, and when the computer-readable storage medium runs on a computer, the computer is caused to execute the network address allocation method and the subnet allocation method described in the above embodiments.
In yet another embodiment provided by the present invention, there is also provided a computer program product containing instructions which, when run on a computer, cause the computer to perform the network address allocation method and subnet allocation method described in the above embodiments.
In the above embodiments, all or part of the implementation may be realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the invention to be performed in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that includes one or more available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid State Disk (SSD)), among others.
It should be noted that, in this document, relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrases "comprising a," "8230," "8230," or "comprising" does not exclude the presence of additional like elements in a process, method, article, or apparatus that comprises the element.
All the embodiments in the present specification are described in a related manner, and the same and similar parts among the embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
The above description is only for the preferred embodiment of the present invention, and is not intended to limit the 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 (15)
1. A network address allocation method is characterized in that the method is applied to a K8S cluster, the K8S cluster comprises a container network interface plug-in, and the container network interface plug-in is connected with a virtual network control plane of IaaS; the K8S cluster further comprises at least one container cluster, and the container network interface plug-in is used for allocating network addresses to the container cluster; the method comprises the following steps:
the container network interface plug-in sends a subnet application request to a virtual network control plane of the IaaS; the subnet application request carries network configuration information; the network configuration information comprises a main network number and a network address number of the subnet; the subnet is a private network applied to the K8S cluster;
receiving configuration confirmation information of the subnet, which is sent by a virtual network control plane of the IaaS; the configuration confirmation information records the network addresses of the number of the network addresses in the subnet corresponding to the main network number;
when a network address acquisition request sent by the container cluster is received, distributing an idle network address in the subnet to the container cluster; the network address is used for providing an access address for an external device to access an application in the container cluster.
2. The method of claim 1, wherein the container network interface plug-in is configured with an unallocated list and an allocated list; the unallocated list is used for recording unallocated network addresses in the network addresses of the subnet; the allocated list is used for recording the allocated network addresses in the network addresses of the subnets;
when a network address acquisition request sent by the container cluster is received, allocating an idle network address in the subnet to the container cluster, including:
when a network address acquisition request sent by the container cluster is received, judging whether the network address exists in the unallocated list or not;
if the network address exists in the unallocated list, determining the network address at the head of the unallocated list as a target network address;
assigning the target network address to the cluster of containers.
3. The method according to claim 2, wherein after the step of allocating a network address free in the subnet to the container cluster when receiving a network address acquisition request sent by the container cluster, the method further comprises:
deleting the target network address in the unallocated list and recording the target network address in the allocated list.
4. The method according to claim 1, wherein after the step of receiving the configuration confirmation information of the subnet sent by the virtual network control plane of IaaS, the method further comprises:
creating an unallocated list and an allocated list;
adding a network address of the number of network addresses of the subnet to the unallocated list.
5. The method according to claim 2, wherein after the step of allocating a network address free in the subnet to the container cluster when receiving a network address acquisition request sent by the container cluster, the method further comprises:
receiving a network address release request sent by the container cluster; the network address release request is recorded with the target network address;
judging whether the target network address exists in the distributed list or not;
and if the target network address exists, deleting the target network address in the allocated list and recording the target network address at the tail part of the unallocated list.
6. A subnet distribution method is characterized in that the method is applied to a virtual network control plane of IaaS, a network managed by the virtual network control plane of the IaaS comprises at least one subnet, and the subnet is configured with at least one network address; the virtual network control plane of the IaaS is connected with a container network interface plug-in of a K8S cluster, the K8S cluster further comprises at least one container cluster, and the container cluster is connected with the container network interface plug-in; the method comprises the following steps:
receiving a subnet application request sent by the container network interface plug-in; the subnet application request carries network configuration information; the network configuration information comprises a main network number and a network address number of the subnet; the subnet is a private network applied to the K8S cluster;
sending the configuration confirmation information of the subnet to the container network interface plug-in; the configuration confirmation information records the network addresses of the number of the network addresses in the subnet corresponding to the main network number; the container network interface plug-in is used for managing the network address in the subnet and distributing the network address to the container cluster when receiving a network address acquisition request sent by the container cluster; the network address is used for providing an access address for an external device to access an application in the container cluster.
7. The method of claim 6, wherein after the step of sending the configuration confirmation information for the subnet to the container network interface plug-in, the method further comprises:
and marking the network addresses of the network address number in the virtual network control plane of the IaaS as allocated states.
8. The network address allocation device is applied to a K8S cluster, wherein the K8S cluster comprises a container network interface plug-in, and the container network interface plug-in is connected with a virtual network control plane of IaaS; the K8S cluster further comprises at least one container cluster, and the container network interface plug-in is used for allocating network addresses to the container cluster; the device comprises:
a first sending module, configured to send, by the container network interface plug-in, a subnet application request to a virtual network control plane of the IaaS; the subnet application request carries network configuration information; the network configuration information comprises a main network number and a network address number of the subnet; the subnet is a private network applied to the K8S cluster;
a first receiving module, configured to receive configuration confirmation information of the subnet, which is sent by a virtual network control plane of the IaaS; the configuration confirmation information records the network addresses of the number of the network addresses in the subnet corresponding to the main network number;
the distribution module is used for distributing idle network addresses in the sub-network to the container cluster when receiving a network address acquisition request sent by the container cluster; the network address is used for providing an access address for an external device to access an application in the container cluster.
9. The apparatus of claim 8, wherein the container network interface plug-in is configured with an unallocated list and an allocated list; the unallocated list is used for recording unallocated network addresses in the network addresses of the subnet; the allocated list is used for recording the allocated network addresses in the network addresses of the sub-networks;
the distribution module includes:
the judging submodule is used for judging whether the network address exists in the unallocated list or not when a network address obtaining request sent by the container cluster is received;
a target network address determining submodule, configured to determine, if the network address exists in the unallocated list, the network address at the head of the unallocated list as a target network address;
an assignment submodule for assigning the target network address to the container cluster.
10. The apparatus of claim 9, further comprising:
a first update module to delete the target network address in the unallocated list and to record the target network address in the allocated list.
11. The apparatus of claim 8, further comprising:
the creation module is used for creating an unallocated list and an allocated list;
an adding module for adding the network addresses of the number of network addresses of the subnet to the unassigned list.
12. The apparatus of claim 9, further comprising:
a second receiving module, configured to receive a network address release request sent by the container cluster; the network address release request is recorded with the target network address;
a judging module, configured to judge whether the target network address exists in the allocated list;
and the second updating module is used for deleting the target network address in the allocated list and recording the target network address at the tail part of the unallocated list if the target network address exists.
13. A subnet distribution apparatus, which is characterized in that a virtual network control plane applied to IaaS, a network managed by the virtual network control plane of IaaS includes at least one subnet, and the subnet is configured with at least one network address; the virtual network control plane of the IaaS is connected with a container network interface plug-in of a K8S cluster, the K8S cluster further comprises at least one container cluster, and the container cluster is connected with the container network interface plug-in; the device comprises:
a third receiving module, configured to receive a subnet application request sent by the container network interface plug-in; the subnet application request carries network configuration information; the network configuration information comprises a main network number and a network address number of the subnet; the subnet is a private network applied to the K8S cluster;
the second sending module is used for sending the configuration confirmation information of the subnet to the container network interface plug-in; the configuration confirmation information records the network addresses of the number of the network addresses in the subnet corresponding to the main network number; the container network interface plug-in is used for managing the network address in the subnet and distributing the network address to the container cluster when receiving a network address acquisition request sent by the container cluster; the network address is used for providing an access address for an external device to access an application in the container cluster.
14. An electronic device, comprising a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus;
the memory is used for storing a computer program;
the processor, when executing a program stored on the memory, implementing the method of any one of claims 1-7.
15. One or more computer-readable media having instructions stored thereon that, when executed by one or more processors, cause the processors to perform the method recited in any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310052249.6A CN115801733A (en) | 2023-02-02 | 2023-02-02 | Network address allocation method and device, electronic equipment and readable medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310052249.6A CN115801733A (en) | 2023-02-02 | 2023-02-02 | Network address allocation method and device, electronic equipment and readable medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115801733A true CN115801733A (en) | 2023-03-14 |
Family
ID=85429522
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310052249.6A Pending CN115801733A (en) | 2023-02-02 | 2023-02-02 | Network address allocation method and device, electronic equipment and readable medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115801733A (en) |
Citations (20)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102316447A (en) * | 2011-09-14 | 2012-01-11 | 福建星网锐捷网络有限公司 | Internet protocol (IP) address allocation and sending method, wireless access device, server and system |
| CN102413203A (en) * | 2011-12-01 | 2012-04-11 | 中兴通讯股份有限公司 | IP (Internet Protocol) address allocation method and device |
| CN102769678A (en) * | 2012-07-23 | 2012-11-07 | 杭州华三通信技术有限公司 | DHCP (Dynamic Host Configuration Protocol) address distributing method and device |
| CN107580083A (en) * | 2017-09-20 | 2018-01-12 | 北京京东尚科信息技术有限公司 | A kind of method and system of container IP address distribution |
| CN109743261A (en) * | 2019-01-07 | 2019-05-10 | 中国人民解放军国防科技大学 | SDN-based container network resource scheduling method |
| US20210328858A1 (en) * | 2020-04-16 | 2021-10-21 | Ribbon Communications Operating Company, Inc. | Communications methods and apparatus for migrating a network interface and/or ip address from one pod to another pod in a kubernetes system |
| CN113766042A (en) * | 2021-01-20 | 2021-12-07 | 北京沃东天骏信息技术有限公司 | Container address configuration method, system, device, equipment and medium |
| US20220038368A1 (en) * | 2020-07-29 | 2022-02-03 | Vmware, Inc. | Flow tracing operation in container cluster |
| US20220038501A1 (en) * | 2020-07-29 | 2022-02-03 | Vmware, Inc. | Connection tracking for container cluster |
| CN114070822A (en) * | 2021-11-17 | 2022-02-18 | 苏州博纳讯动软件有限公司 | Kubernetes Overlay IP address management method |
| CN114172802A (en) * | 2021-12-01 | 2022-03-11 | 百果园技术(新加坡)有限公司 | Container network configuration method and device, computing node, main node and storage medium |
| CN114237812A (en) * | 2021-11-10 | 2022-03-25 | 上海浦东发展银行股份有限公司 | Container network management system |
| CN114339748A (en) * | 2020-09-30 | 2022-04-12 | 华为技术有限公司 | Authentication method and device |
| CN114500462A (en) * | 2020-11-12 | 2022-05-13 | 阿里巴巴集团控股有限公司 | Virtual private cloud network address allocation method and device, electronic equipment and medium |
| US20220278927A1 (en) * | 2021-03-01 | 2022-09-01 | Juniper Networks, Inc. | Data interfaces with isolation for containers deployed to compute nodes |
| CN115174529A (en) * | 2021-03-18 | 2022-10-11 | 北京金山云网络技术有限公司 | Network processing method and device, electronic equipment and storage medium |
| CN115314468A (en) * | 2022-08-05 | 2022-11-08 | 成都道客数字科技有限公司 | IP address allocation method and system for container cloud platform |
| CN115314353A (en) * | 2022-08-10 | 2022-11-08 | 中电云数智科技有限公司 | Device and method for realizing single-pod multi-network card based on kubernets |
| CN115334018A (en) * | 2022-08-12 | 2022-11-11 | 太保科技有限公司 | Openstack-based container control method and device for IaaS cloud architecture and container |
| CN115665026A (en) * | 2022-09-26 | 2023-01-31 | 京东科技信息技术有限公司 | Cluster networking method and device |
-
2023
- 2023-02-02 CN CN202310052249.6A patent/CN115801733A/en active Pending
Patent Citations (20)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102316447A (en) * | 2011-09-14 | 2012-01-11 | 福建星网锐捷网络有限公司 | Internet protocol (IP) address allocation and sending method, wireless access device, server and system |
| CN102413203A (en) * | 2011-12-01 | 2012-04-11 | 中兴通讯股份有限公司 | IP (Internet Protocol) address allocation method and device |
| CN102769678A (en) * | 2012-07-23 | 2012-11-07 | 杭州华三通信技术有限公司 | DHCP (Dynamic Host Configuration Protocol) address distributing method and device |
| CN107580083A (en) * | 2017-09-20 | 2018-01-12 | 北京京东尚科信息技术有限公司 | A kind of method and system of container IP address distribution |
| CN109743261A (en) * | 2019-01-07 | 2019-05-10 | 中国人民解放军国防科技大学 | SDN-based container network resource scheduling method |
| US20210328858A1 (en) * | 2020-04-16 | 2021-10-21 | Ribbon Communications Operating Company, Inc. | Communications methods and apparatus for migrating a network interface and/or ip address from one pod to another pod in a kubernetes system |
| US20220038368A1 (en) * | 2020-07-29 | 2022-02-03 | Vmware, Inc. | Flow tracing operation in container cluster |
| US20220038501A1 (en) * | 2020-07-29 | 2022-02-03 | Vmware, Inc. | Connection tracking for container cluster |
| CN114339748A (en) * | 2020-09-30 | 2022-04-12 | 华为技术有限公司 | Authentication method and device |
| CN114500462A (en) * | 2020-11-12 | 2022-05-13 | 阿里巴巴集团控股有限公司 | Virtual private cloud network address allocation method and device, electronic equipment and medium |
| CN113766042A (en) * | 2021-01-20 | 2021-12-07 | 北京沃东天骏信息技术有限公司 | Container address configuration method, system, device, equipment and medium |
| US20220278927A1 (en) * | 2021-03-01 | 2022-09-01 | Juniper Networks, Inc. | Data interfaces with isolation for containers deployed to compute nodes |
| CN115174529A (en) * | 2021-03-18 | 2022-10-11 | 北京金山云网络技术有限公司 | Network processing method and device, electronic equipment and storage medium |
| CN114237812A (en) * | 2021-11-10 | 2022-03-25 | 上海浦东发展银行股份有限公司 | Container network management system |
| CN114070822A (en) * | 2021-11-17 | 2022-02-18 | 苏州博纳讯动软件有限公司 | Kubernetes Overlay IP address management method |
| CN114172802A (en) * | 2021-12-01 | 2022-03-11 | 百果园技术(新加坡)有限公司 | Container network configuration method and device, computing node, main node and storage medium |
| CN115314468A (en) * | 2022-08-05 | 2022-11-08 | 成都道客数字科技有限公司 | IP address allocation method and system for container cloud platform |
| CN115314353A (en) * | 2022-08-10 | 2022-11-08 | 中电云数智科技有限公司 | Device and method for realizing single-pod multi-network card based on kubernets |
| CN115334018A (en) * | 2022-08-12 | 2022-11-11 | 太保科技有限公司 | Openstack-based container control method and device for IaaS cloud architecture and container |
| CN115665026A (en) * | 2022-09-26 | 2023-01-31 | 京东科技信息技术有限公司 | Cluster networking method and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108897628B (en) | Method and device for realizing distributed lock and electronic equipment | |
| CN103078965B (en) | The IP address management method of virtual machine | |
| CN111212134A (en) | Request message processing method and device, edge computing system and electronic equipment | |
| CN110740057B (en) | Service deployment method and block chain platform | |
| US10282120B2 (en) | Method, apparatus and system for inserting disk | |
| CN105045762A (en) | Management method and apparatus for configuration file | |
| CN111163186B (en) | ID generation method, device, equipment and storage medium | |
| WO2023056797A1 (en) | Blockchain-based data processing method, apparatus, and device, and storage medium | |
| CN103369038A (en) | PaaS (platform as a service) management platform and method | |
| CN111064786B (en) | Account identifier management method and device | |
| CN113361913A (en) | Communication service arranging method, device, computer equipment and storage medium | |
| US9160705B2 (en) | Identifier management | |
| CN112035244A (en) | Deployment of virtual node clusters in a multi-tenant environment | |
| CN111435341A (en) | Enhanced management of repository availability in a virtual environment | |
| CN105208137A (en) | Internet Protocol (IP) address allocation methods, device, server and terminal | |
| CN113010897A (en) | Cloud computing security management method and system | |
| CN115801733A (en) | Network address allocation method and device, electronic equipment and readable medium | |
| CN111683164B (en) | IP address configuration method and VPN service system | |
| CN115174529B (en) | Network processing method and device, electronic equipment and storage medium | |
| CN115562871A (en) | Memory allocation management method and device | |
| TW202315360A (en) | Microservice allocation method, electronic equipment, and storage medium | |
| CN113542013A (en) | Method, device and equipment for distributing virtualized network function management messages | |
| CN113347046A (en) | Network access method and device | |
| CN113114571A (en) | Data packet processing method and device, electronic equipment and storage medium | |
| CN112241307A (en) | Virtual machine creation method and device and related equipment |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20230314 |