Bringing Up Client and CSRX Pods
Let’s create two virtual networks using this YAML file:
# cat vn-left.yaml
apiVersion: k8s.cni.cncf.io/v1
kind:
NetworkAttachment
Definition metadata:
annotations:
opencontrail.org/cidr:
"10.10.10.0/24"
opencontrail.org/ip_fabric
_forwarding: "false"
opencontrail.org/ip_fabric_
snat: "false"
name: vn-left
namespace:
default
spec:
config: '{ "cniVersion": "0.3.0", "type": "contrail-k8s-cni"
}'
# cat vn-right.yaml
apiVersion:
k8s.cni.cncf.io/v1
kind:
NetworkAttachment
Definition metadata:
annotations:
opencontrail.org/cidr:
"10.20.20.0/24"
opencontrail.org/ip_fabric_
forwarding: "false"
opencontrail.org/ip_fabric_
snat: "false"
name: vn-right
namespace:
default
spec:
config: '{ "cniVersion": "0.3.0",
"type": "contrail-k8s-cni" }' #
kubectl create -f vn-left.yaml
# kubectl create -f vn-right.yaml
Verify using Kubectl:
# kubectl get network-
attachment-definition
NAME AGE
vn-left
19d vn-right
17d
# kubectl describe network-
attachment-definition
Name: vn-left
Namespace:
default Labels: <none>
Annotations: opencontrail.org/cidr: 10.10.10.0/24
opencontrail.org/ip_fabric_forwarding:
false opencontrail.org/ip_fabric_snat: false
API Version: k8s.cni.cncf.io/v1
Kind:
NetworkAttachment Definition
Metadata:
Creation Timestamp:
2019-05-25T20:28:22Z
Generation: 1
Resource Version: 83111
Self Link: /apis/k8s.cni.cncf.io/v1/namespaces/default/network-attachment-definitions/vn-left
UID: a44fe276-
7f2b-11e9-9ff0-0050569e2171
Spec:
Config: { "cniVersion": "0.3.0",
"type": "contrail-k8s-cni" } Events:
<none>
Name: vn-right
Namespace: default
Labels: <none>
Annotations: opencontrail.org/cidr: 10.20.20.0/24 opencontrail.org/ip_fabric_forwarding:
false
opencontrail.org/ip_fabric_snat: false API Version: k8s.cni.cncf.io/v1
Kind:
NetworkAttachmentDefinition
Metadata:
Creation Timestamp: 2019-05-28T07:14:02Z
Generation: 1
Resource Version: 380427
Self Link: /apis/k8s.cni.cncf.io/v1/namespaces/default/network-attachment-definitions/vn-right
UID: 2b8d394f-8118-11e9-b36d-0050569e2171
Spec: Config: { "cniVersion": "0.3.0", "type": "contrail-k8s-cni"
} Events:
<none>
It’s good practice to confirm that these two networks are now in Contrail before proceeding. From the Contrail UI, select Configure > Networking > Networks > default-domain > k8s-default is shown in Figure 1, which focuses on the left network.
If you use the default namespace in the YAML file for a network, it will create it in the domain default-domain and project k8s-default.
