Install Single Cluster Multi-Network CN2
SUMMARY See examples on how to install single cluster CN2 in a deployment where Kubernetes traffic and CN2 traffic go over separate networks.
In a single cluster multi-network deployment:
-
CN2 is the networking platform and CNI plug-in for that cluster. The Contrail controller runs in the Kubernetes control plane, and the Contrail data plane components run on all nodes in the cluster.
-
Cluster traffic is separated onto two networks. The Kubernetes control plane traffic traverses one network while Contrail control and data traffic traverse the second network. It's also possible (but less common) to separate traffic onto more than two networks, but this is beyond the scope of these examples.
Figure 1 shows the cluster that you'll create if you follow this single cluster multi-network example. The cluster consists of a single control plane node, two worker nodes, and two subnets.
All nodes shown can be VMs or bare metal servers.
Kubernetes control plane traffic goes over the 172.16.0.0/24 fabric virtual network while Contrail control and data traffic go over the 10.16.0.0/24 fabric virtual network. The fabric networks provide the underlay over which the cluster runs.
The local administrator is shown attached to a separate network reachable through a gateway. This is typical of many installations where the local administrator manages the fabric and cluster from the corporate LAN. In the procedures that follow, we refer to the local administrator station as your local computer.
Connecting all cluster nodes together is the data center fabric, which is shown in the example as two subnets. In real installations, the data center fabric is a network of spine and leaf switches that provide the physical connectivity for the cluster.
In an Apstra-managed data center, this connectivity would be specified through the overlay virtual networks that you create across the underlying fabric switches.
The procedures in this section show basic examples of how you can use the provided manifests to create the specified CN2 deployment. You're not limited to the deployment described in this section nor are you limited to using the provided manifests. CN2 supports a wide range of deployments that are too numerous to cover in detail. Use the provided examples as a starting point to roll your own manifest tailored to your specific situation.
Release | Kernel Mode Data Plane | DPDK Data Plane |
---|---|---|
22.4 | Install Single Cluster Multi-Network CN2 Running Kernel Mode Data Plane in Release 22.4 | Install Single Cluster Multi-Network CN2 Running DPDK Data Plane in Release 22.4 |
Note:
The provided manifests may not be compatible between releases. Make sure you use the manifests for the release that you're running. |
Install Single Cluster Multi-Network CN2 Running Kernel Mode Data Plane in Release 22.4
Use this procedure to install CN2 in a single cluster multi-network deployment running a kernel mode data plane in release 22.4.
The manifest that you will use in this example procedure is single-cluster/single_cluster_deployer_example.yaml. The procedure assumes that you've placed this manifest into a manifests directory.
Install Single Cluster Multi-Network CN2 Running DPDK Data Plane in Release 22.4
Use this procedure to install CN2 in a single cluster multi-network deployment running a DPDK data plane in release 22.4.
The manifest that you will use in this example procedure is single-cluster/single_cluster_deployer_example.yaml. The procedure assumes that you've placed this manifest into a manifests directory.