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
Copy file name to clipboardExpand all lines: device_plugins/deploy_qat.md
+32Lines changed: 32 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -76,6 +76,38 @@ Users can use the steps below to customize the QAT resource configuration:
76
76
77
77
2. Create QAT device plugin CR with -provisioning-config set as the name of the ConfigMap (created in step 1) in the qat_device_plugin.yaml file or set ConfigMap name in the provisioning-config option from web console.
78
78
79
+
# Multiple Custom Resources
80
+
81
+
The [feature](https://github.com/intel/intel-device-plugins-for-kubernetes/tree/main/cmd/operator#multiple-custom-resources) can be used with a `nodeSelector` label representing the capabilities supported on the node. Multiple custom resources on nodes can be supported with different QAT capabilities.
82
+
83
+
* For example, to assign the capability `sym` for a node: create the label on the node
84
+
```
85
+
oc label node <node_name> qat.mode=sym
86
+
```
87
+
* Deploy a new `QatDevicePlugin` Custom resource by adding the above label as a `nodeSelector` and choosing the configmap created with `sym` capability according to [QAT Resource Configuration](#qat-resource-configuration-experimental):
To run the Intel QAT based workloads as an unprivileged pod (see [issue](https://github.com/intel/intel-technology-enabling-for-openshift/issues/122)). The customized `qat-scc` Security Context Constraint (SCC) is provided to bind with service account and run the QAT based workload.
0 commit comments