security: update yum repo

fix node's annotations overwrited incorrectly

fix #376

Fix typo in multi-nic.md

s/eht0/eth0

Userspace-CNI updates in dpdk.md

Show users how to mount a directory containing only the socket files
that are relevant to a pod.

Some small tidy up of the doc.

Reduce DPDK image size

Blank lines within a RUN result in empty continuation line warning
during Docker build. Remove these empty lines.

security: update loopback to fix CVE

Script checks if CONFIG_FILE exists, if not create one with default
values. However, if /opt/ovs-config/ directory does not exist then
the print command fails. mkdir -p creates dir if it does not exist.

Now multistage build
Changed DPDK from make to meson-ninja build
Configured out some unused DPDK options
Image size reduced from 3.2GB to 724MB

fix: add back privilege for ipv6

Config support for OVS-DPDK

security: add trivy scan and fix image CVEs

refactor: use ovs.Exec replace raw command

chore: add gosec to audit code security

chore: prepare for release 1.2

chore: prepare for release 1.2

Add OVS-DPDK support, for issue 104

Documented hugepages configuration
Documented small section on cpu-mask
Documented running TestPMD

Slight reduction in Docker image size,
without any changes to OVS-DPDK, yet.

This commit adds OVS-DPDK support to Kube-OVN. User instructions are
included in a new file docs/dpdk.md

A new Dockerfile has been added to include OVS-DPDK along with OVN.
Where DPDK is required, this image is used for the ovs-ovn pod, in
place of the existing kernel-OVS “kube-ovn” image. This Dockerfile is
currently based on Fedora 32 for reasons noted as comments within the
file. It should later be possible to change this to CentOS when full
DPDK 19 support is available.

I recommend the above Dockerfile is built and tagged as
kube-ovn-dpdk:<version>, where the version corresponds to the DPDK
version used within the image (in this case 19:11) rather than the
Kube-OVN version. I recommend this as DPDK applications have a strong
dependency on DPDK version. If we force an end user to always use the
latest version, then we will likely break their DPDK app. I propose
over time we provide images for multiple DPDK versions and let the user
pick to suit their needs. I don’t see these images or Dockerfiles
requiring maintenance or support. They should be completely independent
of Kube-OVN versions and releases.

The install.sh script has been modified. It now takes a flag
--with-dpdk=<version> so the user can indicate they want to install
OVS-DPDK based on which version of DPDK. Version of DPDK required will
determine version of OVS and this will be already built into the Docker
image provided. The Kube-OVN version installed is still set at the top
of the script as the VERSION variable. This should still be the case
going forward, Kube-OVN and DPDK versions should operate independently
of each other. However, it’s something to watch. If future versions of
Kube-OVN have a strong dependency on newer versions of OVS, then the
older version of OVS used for DPDK may become an issue. We may have to
update the install script so a user wanting an older version of DPDK
has no choice but to use an older version of Kube-OVN that’s known to
be compatible. I don’t foresee this being an issue, but one to watch as
I said.

New startup and healthcheck scripts added for OVS-DPDK.

fix: pod get deleted between configure nb and patch pod

Sometimes pod get deleted between configure nb and patch pod.
Then we need to recycle resources again.

fix: native vlan and delete subnet issues