-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow configuration of Multus dynamic networking plugin #1804
Comments
Hi, can you please provide example of the difference you rendered manually ? |
Hi, essentially I think it's the difference between these two manifests:
From the Readme:
When I installed the plugin using this operator the CRIO version was installed, but as my cluster used containerd it didn't work, I was unable to edit the configmap mentioned in the docs as the operator just replaced it. |
I think we can change the API to plumb a socket instead of using different atributes. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with /lifecycle rotten |
Is your feature request related to a problem? Please describe:
The default configmap for Multus dynamic networking plugin has settings which I need to change - specifically CRIO type and the CRIO socket location
Describe the solution you'd like:
It would be great if those config entries could be configured in the operator config, alternatively a feature like you have for one of the other plugins (macvtap?) where you can specify an alternative ConfigMap to use would also work
Describe alternatives you've considered:
Installing Multus and the dynamic network plugin manually is an option, renders this operator a bit redundant though :)
The text was updated successfully, but these errors were encountered: