Add ovn4nfv addon helm chart 33/120033/4
authorTodd Malsbary <todd.malsbary@intel.com>
Mon, 1 Mar 2021 23:13:08 +0000 (15:13 -0800)
committerTodd Malsbary <todd.malsbary@intel.com>
Tue, 4 May 2021 21:41:48 +0000 (14:41 -0700)
commit61dc8e7b3aa13852dfde84dad4e6152178dd298d
tree52ef38d3b13df5355517ae54a51736a8a6d919ff
parentc7cc63c3e76d5739c67314008b01f6fe70289641
Add ovn4nfv addon helm chart

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
21 files changed:
kud/deployment_infra/helm/ovn4nfv/.helmignore [new file with mode: 0644]
kud/deployment_infra/helm/ovn4nfv/Chart.yaml [new file with mode: 0644]
kud/deployment_infra/helm/ovn4nfv/crds/network.yaml [new file with mode: 0644]
kud/deployment_infra/helm/ovn4nfv/crds/networkchaining.yaml [new file with mode: 0644]
kud/deployment_infra/helm/ovn4nfv/crds/providernetwork.yaml [new file with mode: 0644]
kud/deployment_infra/helm/ovn4nfv/templates/_helpers.tpl [new file with mode: 0644]
kud/deployment_infra/helm/ovn4nfv/templates/clusterrole.yaml [new file with mode: 0644]
kud/deployment_infra/helm/ovn4nfv/templates/clusterrolebinding.yaml [new file with mode: 0644]
kud/deployment_infra/helm/ovn4nfv/templates/configmap.yaml [new file with mode: 0644]
kud/deployment_infra/helm/ovn4nfv/templates/daemonset.yaml [new file with mode: 0644]
kud/deployment_infra/helm/ovn4nfv/templates/deployment.yaml [new file with mode: 0644]
kud/deployment_infra/helm/ovn4nfv/templates/ovn/daemonset.yaml [new file with mode: 0644]
kud/deployment_infra/helm/ovn4nfv/templates/ovn/deployment.yaml [new file with mode: 0644]
kud/deployment_infra/helm/ovn4nfv/templates/ovn/service.yaml [new file with mode: 0644]
kud/deployment_infra/helm/ovn4nfv/templates/service.yaml [new file with mode: 0644]
kud/deployment_infra/helm/ovn4nfv/templates/serviceaccount.yaml [new file with mode: 0644]
kud/deployment_infra/helm/ovn4nfv/values.yaml [new file with mode: 0644]
kud/hosting_providers/containerized/inventory/group_vars/k8s-cluster.yml
kud/hosting_providers/vagrant/inventory/group_vars/k8s-cluster.yml
kud/tests/_common.sh
kud/tests/ovn4nfv.sh