Deprecating the kubevirt-config configmap

[Roman Mohr]

Hi,

For some releases now we have added the option to add the content of `kubevirt-config` into the KubeVirt CR. Since 0.34.2 the schema of  the config is stable and can be used instead of the config map.

The user-guide is now also up-to-date and you can transfer over your configurations from the config map to the KubeVirt CR. [1]

Will my kubevirt-config still be recognized on releases after 0.34.2?

Yes, it will have for about 6 months precedence over configurations on the KubeVirt CR.
This should give you enough time to transfer your configuration over.

New configuration options will only be added to the CR. The first feature affected by this is PCI passthrough which can only be configured on the CR.

How do I move my configuration from the ConfigMap to the CR?

The schema is now  fully documented in our api-reference [2].

You can do the following:

1) kubectl edit kubevirt -n kubevirt kubevirt
2) Fill out the config as described in the schema [2]
3) Delete your config-map: kubectl delete configmap -n kubevirt kubevirt-config

I am still not using the kubevirt operator, how can I migrate?

You will have to register the KubeVirt CR manually and give our components read/list/watch access toe kubevirt CRs in the install namespace. They will then pick it up. No operator is needed.

Can you give me an example for reference?

Yes, here is the KubeVirt CR which enables some feature gates:

```
apiVersion: kubevirt.io/v1alpha3
kind: KubeVirt
metadata:
  name: kubevirt
  namespace: kubevirt
spec:
  configuration:
    developerConfiguration:
      featureGates:
      - CPUManager
      - LiveMigration
      - ExperimentalIgnitionSupport
      - Sidecar
      - Snapshot
      - HotplugVolumes
```

Let me know if you have more questions.

Best Regards,
Roman

[1] https://github.com/kubevirt/user-guide/pull/333
[2] https://kubevirt.io/api-reference/master/definitions.html#_v1_kubevirtconfiguration