aboutsummaryrefslogtreecommitdiffstats
path: root/kud/deployment_infra/helm/ovn4nfv/templates/daemonset.yaml
AgeCommit message (Collapse)AuthorFilesLines
2021-05-19Mount /var/run as sharedTodd Malsbary1-0/+1
This fixes the "unknown FS magic" error reported by nfn-agent: E0518 22:05:58.596460 20593 cni.go:150] Failed to configure interface in pod: failed to open netns "/var/run/netns/cni-c24e4d8e-819c-6a0c-9ae5-6b4e5cf8f68d": unknown FS magic on "/var/run/netns/cni-c24e4d8e-819c-6a0c-9ae5-6b4e5cf8f68d": 1021994 It can be observed as a failure of the ovn4nfv.sh test when CONTAINER_RUNTIME is "containerd". Issue-ID: MULTICLOUD-1324 Signed-off-by: Todd Malsbary <todd.malsbary@intel.com> Change-Id: If979110d125511827a65a5de5101a2832d5efeb5
2021-05-04Add ovn4nfv addon helm chartTodd Malsbary1-0/+168
This chart follows the upstream installation guide with the following exceptions: - The node-role.kubernetes.io/master:NoSchedule taint is not removed. The YAML files already included the necessary tolerations. - No node labeling is done. Instead, the ovn-control-plane node selector is for the master role, and the nfn-operator pod affinity is for "role: ovn-control-plane". This ensures that the ovn-control-plane and nfn-operator run are scheduled on the same master node, equivalent to the labelling approach used upstream. Also, additional allowed capabilities are needed to run the pods with the restricted PodSecurityPolicy. These capabilities are requested by the Pods, but not available in the default set of allowed capabilities. Issue-ID: MULTICLOUD-1324 Signed-off-by: Todd Malsbary <todd.malsbary@intel.com> Change-Id: I54ae12434572e2e2dd1fe2ec9298d04557331d94