Network segmentation for container orchestration platforms

1. A network controller comprising:

a memory configured to store a request, conforming to a container orchestration platform, to configure a new pod of a plurality of pods with a primary interface to communicate on a virtual network to segment a network formed by the plurality of pods, wherein by default the primary interface is defined by the container orchestration platform strictly to communicate with every other pod of the plurality of pods via a default pod network; and

processing circuitry configured to configure, responsive to the request, the new pod with a custom resource that redefines the primary interface that results in a redefined primary interface, the redefined primary interface configured to communicate via the virtual network while still providing at least a portion of default primary interface functionality defined by the container orchestration platform.

2. The network controller of claim 1 , wherein the processing circuitry is configured to, when configured to configure the new pod, configure the primary interface to enable communications via the virtual network without being configured to communicate with the default pod network.

3. The network controller of claim 2 , wherein the custom resource redefines the primary interface to enable the communications via the virtual network and not the default pod network.

4. The network controller of claim 1 ,

wherein the request comprises a first request,

wherein the virtual network comprises a first virtual network,

wherein the processing circuitry is further configured to process a second request to create a virtual network router,

wherein the virtual network router is configured to cause the network controller to interconnect the first virtual network and a second virtual network of the network formed by the plurality of pods,

wherein the virtual network router represents a logical abstraction of one or more policies that cause one or more of import and export of routing information between the first virtual network and the second virtual network, and

wherein the processing circuitry is further configured to configure the first virtual network and the second virtual network according to the one or more policies to enable one or more of the import and the export of routing information between the first virtual network and the second virtual network via the virtual network router.

5. The network controller of claim 4 ,

wherein the second request includes a label associated with the first virtual network and the second virtual network, and

wherein the processing circuitry identifies, based on the label, the first virtual network and the second virtual network in order to configure a routing instance corresponding to the virtual network router, in accordance with the one or more policies, to cause the import and the export of the routing information between the first virtual network and the second virtual network.

6. The network controller of claim 4 ,

wherein the second request indicates that the virtual network router is a mesh virtual network router, and

wherein the one or more policies represented by the mesh virtual network router include symmetrical import and export policies that cause both the import and the export of the routing information between the first virtual network and the second virtual network.

7. The network controller of claim 4 ,

wherein the second request indicates that the virtual network router is a hub virtual network router, the first virtual network is a first spoke virtual network, and the second virtual network is a second spoke virtual network, and

wherein the one or more policies represented by the hub virtual network router include asymmetrical import and export policies that cause export of the routing information from both of the first spoke virtual network and the second spoke virtual network to the virtual network router but no import of the routing information between the first spoke virtual network and the second spoke virtual network.

8. The network controller of claim 1 ,

wherein the memory stores a pod manifest annotation for the new pod that identifies the virtual network on which the redefined primary interface configured for the new pod is to communicate, and

wherein the processing circuitry processes the request to resolve the pod manifest annotation to identify the virtual network on which the redefined primary interface configured for the new pod is to communicate.

9. The network controller of claim 1 , wherein a namespace identifies the virtual network on which the redefined primary interface configured for the new pod is to communicate.

10. A method comprising:

storing, by a network controller, a request conforming to a container orchestration platform by which to configure a new pod of a plurality of pods with a primary interface to communicate on a virtual network to segment a network formed by the plurality of pods, wherein by default the primary interface is defined by the container orchestration platform strictly to communicate with every other pod of the plurality of pods via a default pod network; and

configuring, by the network controller, and responsive to the request, the new pod with a custom resource that redefines the primary interface that results in a redefined primary interface, the primary interface configured to communicate via the virtual network while still providing at least a portion of default primary interface functionality defined by the container orchestration platform.

11. The method of claim 10 , wherein configuring the new pod comprises configuring the redefined primary interface to enable communications via the virtual network without being configured to communicate with the default pod network.

12. The method of claim 11 , wherein the request indicates that the container orchestration platform is to configure the new pod with the custom resource that redefines the primary interface to enable the communications via the virtual network and not the default pod network.

13. The method of claim 10 ,

wherein the request comprises a first request,

wherein the virtual network comprises a first virtual network,

wherein the method further comprises processing a second request by which to create a virtual network router,

wherein the virtual network router is configured to cause the network controller to interconnect the first virtual network and a second virtual network of the network formed by the plurality of pods,

wherein the virtual network router represents a logical abstraction of one or more policies that cause one or more of import and export of routing information between the first virtual network and the second virtual network, and

wherein the method further comprises configuring the first virtual network and the second virtual network according to the one or more policies to enable one or more of the import and the export of routing information between the first virtual network and the second virtual network via the virtual network router.

14. The method of claim 13 ,

wherein the second request includes a label associated with the first virtual network and the second virtual network, and

wherein the network controller identifies, based on the label, the first virtual network and the second virtual network in order to configure a routing instance corresponding to the virtual network router, in accordance with the one or more policies, to cause the import and the export of the routing information between the first virtual network and the second virtual network.

15. The method of claim 13 ,

wherein the second request indicates that the virtual network router is a mesh virtual network router, and

wherein the one or more policies represented by the mesh virtual network router include symmetrical import and export policies that cause both the import and the export of the routing information between the first virtual network and the second virtual network.

16. The method of claim 13 ,

wherein the second request indicates that the virtual network router is a hub virtual network router, the first virtual network is a first spoke virtual network, and the second virtual network is a second spoke virtual network, and

wherein the one or more policies represented by the hub virtual network router include asymmetrical import and export policies that cause export of the routing information from both of the first spoke virtual network and the second spoke virtual network to the virtual network router but no import of the routing information between the first spoke virtual network and the second spoke virtual network.

17. The method of claim 10 , further comprising:

storing a pod manifest annotation for the new pod that identifies the virtual network on which the redefined primary interface configured for the new pod is to communicate; and

processing the request to resolve the pod manifest annotation to identify the virtual network on which the redefined primary interface configured for the new pod is to communicate.

18. A non-transitory computer-readable storage medium storing instructions that when executed, cause processing circuitry to:

store a request conforming to a container orchestration platform by which to configure a new pod of a plurality of pods with a primary interface to communicate on a virtual network to segment a network formed by the plurality of pods, wherein by default the primary interface is defined by the container orchestration platform strictly to communicate with every other pod of the plurality of pods via a default pod network; and

configure, responsive to the request, the new pod with a custom resource that redefines the primary interface that results in a redefined primary interface, the redefined primary interface configured to communicate via the virtual network while still providing at least a portion of default primary interface functionality defined by the container orchestration platform.