When creating a HCP OSV cluster, the storageclass "kubevirt-csi-infra" is automatically the default storageclass (storageclass.kubernetes.io/is-default-class: 'true'). 
The problem is this can not be altered to allow a different storageclass to be the default. On a non-HCP cluster, a different storageclass can be the default by altering the annotation to "true" or "false". 
Any attempt on the kubevirt one results in the default being set back to 'true' since it is managed by the hypershift operator. 
This behavior is contrary to other OCP clusters and has resulted in issues where an application picks the 'default' storageclass and ends up with kubevirt, which is not desirable. 

    4.16 and others

    easy

    1.Create a HCP cluster with kubevirt
    2.Add another potential storageclass
    3.Attempt to change the kubevirt one to not be default via the storageclass yaml annotation.
    

    kubevirt will reset to 'true' as default storageclass

    kubevirt will accept the change to the annotation.