qat init: make conf optional

cmd/qat_plugin/README.md

@@ -136,12 +136,11 @@ In addition to the default configuration, you can add device-specific configurat
 |:-------|:-----------------------|:-----------------|:--------|:------|
 | 4xxx, 401xx,402xx | [cfg_services](https://github.com/torvalds/linux/blob/42e66b1cc3a070671001f8a1e933a80818a192bf/Documentation/ABI/testing/sysfs-driver-qat) reports the configured services (crypto services or compression services) of the QAT device. | `ServicesEnabled=<value>` | compress:`dc`, crypto:`sym;asym` | Linux 6.0+ kernel is required. |
 
-To create a provisioning config after customizing, run as follows:
+To create a provisioning `configMap`, run the following command before deploying initcontainer:
 
 ```bash
 $ kubectl create configmap --namespace=inteldeviceplugins-system qat-config --from-file=deployments/qat_plugin/overlays/qat_initcontainer/qat.conf
 ```
-> **Note**: When deploying the overlay qat_initcontainer, such a manual creation is not necessary since ConfigMap is generated automatically. Just set the values in the config file and deploy the overlay.
 
 When using the operator for deploying the plugin with provisioning config, use `provisioningConfig` field for the name of the ConfigMap, then the config is passed to initcontainer through the volume mount.
 

deployments/qat_plugin/overlays/qat_initcontainer/kustomization.yaml

@@ -2,7 +2,3 @@ bases:
 - ../../base
 patchesStrategicMerge:
 - qat_initcontainer.yaml
-configMapGenerator:
-- name: qat-config
-  files:
-  - qat.conf

deployments/qat_plugin/overlays/qat_initcontainer/qat.conf

@@ -1 +0,0 @@
-ServicesEnabled=sym;asym

deployments/qat_plugin/overlays/qat_initcontainer/qat_initcontainer.yaml

@@ -28,4 +28,5 @@ spec:
       - name: qat-config
         configMap:
           name: qat-config
+          optional: true
           defaultMode: 0440