Automatic configuring of vlan and overlay logical switches for container secondary interfaces
Abstract
The method of some embodiments allocates a secondary network interface for a pod, which has a primary network interface, in a container network operating on an underlying logical network. The method receives an ND that designates a network segment. The method receives the pod, wherein the pod includes an identifier of the ND. The method then creates a secondary network interface for the pod and connects the secondary network interface to the network segment. In some embodiments, the pods include multiple ND identifiers that each identify a network segment. The method of such embodiments creates multiple secondary network interfaces and attaches the multiple network segments to the multiple secondary network interfaces.
Claims
exact text as granted — not AI-modified1 - 8 . (canceled)
9 . A method for configuring a pod, the method comprising:
performing an automated process to associate the pod with at least two network segments, said performing comprising:
detecting deployment of the pod associated with a first network segment, said pod having a default primary interface for connecting to the first network segment;
from a definition of the pod, determining that the pod is to be associated with a second network segment;
identifying a secondary interface for the pod; and
associating the secondary interface with the pod and the second network segment, said secondary interface allowing the pod to communicate with the second network segment.
10 . The method of claim 9 , wherein said determining comprises:
receiving a network attachment definition (NAD) that designates a network segment; and determining that the pod definition includes an identifier of the NAD;
11 . The method of claim 10 , wherein identifying the secondary interface comprises creating the secondary network interface for the pod based on the determination that the pod definition includes the identifier of the NAD.
12 . The method of claim 10 , wherein the NAD designate a pre-created network segment.
13 . The method of claim 10 , wherein the NAD designates attributes of a network segment that the automated process needs to dynamically deploy and to associate the secondary interface with this dynamically deployed network segment.
14 . The method of claim 13 , wherein the dynamically deployed network segment is a VLAN (virtual local area network) segment or an overlay network segment.
15 . The method of claim 10 , wherein the pod definition references a plurality of identifiers for a plurality of NADs to indicate that the pod has a plurality of secondary network interfaces attached to a plurality of network segments.
16 . The method of claim 10 , wherein the NAD comprises a name that is used to identify a network attachment.
17 . The method of claim 10 , wherein the NAD comprises a number or code identifier that identifies the network attachment.
18 . The method of claim 9 , wherein said secondary network interface serves as high-performance interface for data traffic.
19 . A non-transitory machine readable medium storing a program which when executed by at least one processing unit configures a pod, the program comprising sets of instructions for:
detecting deployment of the pod associated with a first network segment, said pod having a default primary interface for connecting to the first network segment; from a definition of the pod, determining that the pod is to be associated with a second network segment; identifying a secondary interface for the pod; and associating the secondary interface with the pod and the second network segment, said secondary interface allowing the pod to communicate with the second network segment.
20 . The non-transitory machine readable medium of claim 19 , wherein the set of instructions for said determining comprises sets of instructions for:
receiving a network attachment definition (NAD) that designates a network segment; and determining that the pod definition includes an identifier of the NAD;
21 . The non-transitory machine readable medium of claim 20 , wherein the set of instructions for identifying the secondary interface comprises a set of instructions for creating the secondary network interface for the pod based on the determination that the pod definition includes the identifier of the NAD.
22 . The non-transitory machine readable medium of claim 20 , wherein the NAD designate a pre-created network segment.
23 . The non-transitory machine readable medium of claim 20 , wherein the NAD designates attributes of a network segment that the automated process needs to dynamically deploy and to associate the secondary interface with this dynamically deployed network segment.
24 . The non-transitory machine readable medium of claim 23 , wherein the dynamically deployed network segment is a VLAN (virtual local area network) segment or an overlay network segment.
25 . The non-transitory machine readable medium of claim 20 , wherein the pod definition references a plurality of identifiers for a plurality of NADs to indicate that the pod has a plurality of secondary network interfaces attached to a plurality of network segments.
26 . The non-transitory machine readable medium of claim 20 , wherein the NAD comprises a name that is used to identify a network attachment.
27 . The non-transitory machine readable medium of claim 20 , wherein the NAD comprises a number or code identifier that identifies the network attachment.
28 . The non-transitory machine readable medium of claim 19 , wherein said secondary network interface serves as high-performance interface for data traffic.Join the waitlist — get patent alerts
Track US2023179484A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.