Skip to content
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.

Sign up for GitHub

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

Jump to bottom

sriov-network-operator should not depend on hardcoded supported device list #86

Open
adrianchiris opened this issue Mar 9, 2021 · 1 comment
Open

sriov-network-operator should not depend on hardcoded supported device list #86

adrianchiris opened this issue Mar 9, 2021 · 1 comment
Labels
enhancement New feature or request

Comments

@adrianchiris
Copy link
Collaborator

The NicIdMap is used for generating device plugin configmap and/or perhaps in other code path (operator-webhook).
If we can find a way to remove all those direct uses of NicIdMap, we could delete it and allows more NICs to be used with SR-IOV Operator directly.

For platforms that wish to limit the devices which the sriov-network-operator operates on, a configMap may be used to provide the list of supported devices.
@adrianchiris adrianchiris added the enhancement New feature or request label Mar 9, 2021
@pliurh
Copy link
Collaborator

pliurh commented Mar 10, 2021

Agree. As OLM has supported ConfigMap operator-framework/operator-lifecycle-manager#1120.

@pliurh pliurh mentioned this issue Jun 17, 2021
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@pliurh @adrianchiris