Disable CRI-O restart by Multus

[basvandenbrink]

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:

/kind api-change
/kind bug
/kind cleanup
/kind design
/kind documentation
/kind failing-test
/kind feature
/kind flake

What this PR does / why we need it:
Currently, Multus is configured to restart CRI-O when Multus is started. According to the Multus docs, this is non-default behaviour and is rarely necessary. Furthermore, restarting CRI-O during the start of CRI-O causes errors on our side.

Error:

2020-11-20T14:38:55+0000 Restarting crio
Failed to get D-Bus connection: Operation not permitted

Quote from the docs:

When using CRIO, you may need to restart CRIO to get the Multus configuration file to take – this is rarely necessary.

--restart-crio=false

https://intel.github.io/multus-cni/doc/how-to-use.html

Which issue(s) this PR fixes:

Fixes #6929

Special notes for your reviewer:

Does this PR introduce a user-facing change?: no

[k8s-ci-robot]

Hi @basvandenbrink. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[floryut]

/ok-to-test
/approve

Ok the doc does indeed says this is rarely necessary, I guess we were mislead by the https://github.com/intel/multus-cni/blob/master/images/multus-daemonset-crio.yml having restart-crio=true 🤷

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: basvandenbrink, floryut

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [floryut]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[floryut]

@basvandenbrink now that #6910 is merged, could you please rebase master ? Thank you!

[basvandenbrink]

/retest

[basvandenbrink]

Did a merge instead of a rebase. Fixed it and force pushed the changes.

[basvandenbrink]

Rebased to include pull rate limit fix.

[LuckySB]

/lgtm