Fix for CRIO Thin Client Installations

[rwlove]

1. Use the correct entrypoint

2. Use /opt/cni/bin for CNI bin dir

[maiqueb]

@s1061123 does this separate crio daemonset spec even makes sense these days ?

[s1061123]

Thank you for the PR, @rwlove !

I make sense the entrypoint fix, however, I'd like to keep '/usr/libexec/cni' for CNI path. There are two reason:

• '/usr/libexec/cni' is the default path of Fedora's CNI plugin path. In Fedora38, for example, dnf install containernetworking-plugins installs CNI plugins into '/usr/libexec/cni'.
• If user uses '/opt/cni/bin' for CNI plugin path, user can use multus-daemonset.yml instead of multus-daemonset-crio.yml because now the difference between '....yml' and '...-crio.yml' (previously we have more difference but now only the CNI path).

So could you please revert the change of CNI path? Thank you again and in advance.

[rwlove]

I understand your feedback and I'll happily update the patch and send a new PR.

[rwlove]

did I update this correctly?

[github-actions]

This pull request is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 7 days.