Before this change, the multus daemonset init container had troubles
with running with SELinux in enforced mode, due to lack of the
container_file_t label on the host /opt/cni/bin directory. Fix that by
making the container privileged.
Ref: rancher/rke2#746
Signed-off-by: Michal Rostecki <mrostecki@opensuse.org>
Adds charts for sriov and multus.
Details:
* Multus chart, on deployment installs number of cnis, not only multus
itself but also other cnis ussually combined with it, like host-device
and macvlan.
* Multus includes a CRD, NetworkAttachmentDefinition, which is the
means to attach interfaces to pods by specifying a delegated cni for
each.
* Multus replaces the existing cni with itself, and sets up a default
NetworkAttachmentDefinition with that existing cni that will setup the
first interface of the pod just as if multus was not there.
* The NetworkAttachmentDefinition CRD is included along other multus
templates in the chart and no specific chart is setup for the CRD.
This CRD is no consumed on deployment and is unlikely to change
frequently.
* Sriov depends on NetworkAttachmentDefinition CRD but no dependency is
set between Multus and Sriov. Sriov charts checks on the presence of
NetworkAttachmentDefinition CRD via capabilities and fails deployment
if unavailable.
* Sriov includes a number of CRDs which are setup as separate chart.
* Sriov operator depends on certificates to be able to deploy its
webhooks. The charts depends and checks for the presence of
cert-manager to generate these certificates. Optionally, via chart
value, cert-manager integration can be disabled in which case the
chart will generate certificates with 1 year validity as a means to
quickly test or trial, but not the intended setup for production
clusters.
Signed-off-by: Jaime Caamaño Ruiz <jcaamano@suse.com>
Signed-off-by: Manuel Buil <mbuil@suse.com>
Brad Davidson
Manuel Buil
Michal Rostecki
Hussein Galal
Jaime Caamaño Ruiz