Configure kata-manager to create the CDI spec, without adding/changing crio configurations

[cclaudio]

In the OpenShift Sandboxed Containers (OSC) operator, the crio configurations are maintained by the OSC operator. If we install the GPU operator with kata-manager enabled, both of them will add crio configurations.

Is there a way to configure the kata-manager to only create the CDI spec, without adding crio configurations? If not, is there any plan to add this feature?

[cclaudio]

$ ls /etc/crio/crio.conf.d/
00-default.conf  50-kata.conf  50-kata-cc.conf 99-nvidia.conf

Currently, kata-manager is always installing 99-nvidia.conf which is a merge of all other drop-in configs. If the 50-kata-cc.conf is removed by its owner, the 99-nvidia.conf will still have the configuration that existed in 50-kata-cc.conf.

Ideally, I think kata-manager should add drop-in configs only for the runtime-classes requested in the ClusterPolicy, if any runtime class was requested.

[cclaudio]

  cdi:
    default: false
    enabled: false
  kataManager:
    config:
      artifactsDir: /opt/nvidia-gpu-operator/artifacts/runtimeclasses
    enabled: true
    env:
    - name: CRIO_CONFIG
      value: mycrio.conf
    image: k8s-kata-manager
    imagePullPolicy: IfNotPresent
    imagePullSecrets: []
    repository: nvcr.io/nvidia/cloud-native
    resources: {}
    version: v0.2.3

When I set CRIO_CONFIG to a value that does not contain /, the kata-manager does not generate or change any crio config in /etc/crio/crio.conf.d/ but it creates the /var/run/cdi/nvidia.com-pgpu.yaml.

Would this be the proper way to configure kata-manager to generate a CDI spec but not crio configs?

[elezar]

@cclaudio separate to the question of how to disable this, we are in the process of reworking the logic of the NVIDIA Container Toolkit to properly support drop-in files (see NVIDIA/nvidia-container-toolkit#1280).

We should also implement this logic here to ensure that a minimal drop-in config is generated instead of a combined one.

[cclaudio]

We should also implement this logic here to ensure that a minimal drop-in config is generated instead of a combined one.

IMHO, that would be the best. Thanks @elezar.

In the meantime, does anybody know what is the recommendation to workaround the issue described in #128 (comment) ? I am wondering if the kata-manager configuration posted in #128 (comment) is a good workaround ?