You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently it appears that the SRIOV resource name are fixed and they are determined based on the underlying device.
When there are servers with multiple accelerator device types, one needs to modify the application deployments to the respective resource name specific to the nodes.
For e.g. before this operator, we used to configure a common name like sriov_acc_resource and add all types of device names as filters for SRIOV to create the resource name. There was a flexibility to use this common resource name across all the application deployments irrespective of the underlying device.
If we could make this configurable so that a user can make his own custom resource yaml based on the device ID but with a common resource name?
The text was updated successfully, but these errors were encountered:
Currently it appears that the SRIOV resource name are fixed and they are determined based on the underlying device.
When there are servers with multiple accelerator device types, one needs to modify the application deployments to the respective resource name specific to the nodes.
For e.g. before this operator, we used to configure a common name like sriov_acc_resource and add all types of device names as filters for SRIOV to create the resource name. There was a flexibility to use this common resource name across all the application deployments irrespective of the underlying device.
If we could make this configurable so that a user can make his own custom resource yaml based on the device ID but with a common resource name?
The text was updated successfully, but these errors were encountered: