The example at step 3 is missing the namespace for the HyperConverged object. If the customer prefers to automate things and not do manual oc edit/patch, then using the YAML example results in incorrect configuration because its missing the namespace and so the configuration ends up in an irrelevant place, not picked up by the operator.

    All

   Always

Try to apply the YAML shown in step 3 and the configuration will end up in whatever namespace is currently selected, not in openshift-cnv where it should go.

    Customer applies the configuration to the wrong namespace after following the examples, which does not have any effect.

    Example should include the namespace

apiVersion: hco.kubevirt.io/v1beta1
kind: HyperConverged
metadata:
  name: kubevirt-hyperconverged
  namespace: openshift-cnv        <---- add this
 spec:
  liveMigrationConfig:
    completionTimeoutPerGiB: 800
    network: <network> 
    parallelMigrationsPerCluster: 5
    parallelOutboundMigrationsPerNode: 2
    progressTimeout: 150
# ...