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 we can configure Node with QAT by creating a configmap with the node name and that gets passed onto the initcontainer and the node is configured.
This does not scale well for a large Clusters with many qat nodes. The users would want to assign say some nodes for compression, some of Crypto and some for mixed.
It would be nice to have a mechanism where the configuration is done with smaller option/configuration and scales with number of nodes. One of the things, we thought about was to use labels. The nodes Labeled for Compression would be configured as compression, Similarly same things could be done for Crypto and mixed. This is just an example, but we things there should be a simpler way to configure that scales with node.
The text was updated successfully, but these errors were encountered:
It would be nice to have a mechanism where the configuration is done with smaller option/configuration and scales with number of nodes
sounds like a nice-to-have at this point but we could look into allowing cluster admins to create multiple CRs so that nodeSelector field can be used to choose which (labeled) nodes the daemonSet is run.
Currently we can configure Node with QAT by creating a configmap with the node name and that gets passed onto the initcontainer and the node is configured.
This does not scale well for a large Clusters with many qat nodes. The users would want to assign say some nodes for compression, some of Crypto and some for mixed.
It would be nice to have a mechanism where the configuration is done with smaller option/configuration and scales with number of nodes. One of the things, we thought about was to use labels. The nodes Labeled for Compression would be configured as compression, Similarly same things could be done for Crypto and mixed. This is just an example, but we things there should be a simpler way to configure that scales with node.
The text was updated successfully, but these errors were encountered: