Alexander Wels

This has been resolved CDI is fully compliant and has a test lane to ensure we remain compliant

The order when uninstalling is important. delete the cr first, then the operator.yaml. Deleting the CR causes the operator to clean up resources. Then you can delete the namespace. If...

Created JIRA card https://issues.redhat.com/browse/CNV-26195 to handle this issue.

Oh yeah everything under cluster-up comes from the [kubevirtci](https://github.com/kubevirt/kubevirtci/blob/main/cluster-up/README.md) repository, maybe open this PR over there, so that when we update kubevirtci over here it automatically gets added?

Well it needs to get updated in kubevirtci first. Once that is merged, we can update kubevirtci in CDI (and also others like kubevirt). This is relevant for more than...

Note we will be updating kubevirtci relatively soon when k8s 1.29 becomes available for test lanes. So it does make sense to put this change in the kubevirtci repo now.

Note you can pass labels to the importer pod using labels on the DataVolumes. Can you explain the use case a little more?

Since it is the garbagecollector deleting the DV, it will also delete the PVC since the DV owns it. That makes sense. But for the garbage collector to delete the...

Okay, well that exhausted my possible ideas. Note that the versions of kubernetes and CDI you are running are very old and we really only support n - 2 so...

So I am wondering, which version of virtctl plugin do you have. I see you are creating a `PVC` with `kubectl virt image-upload pvc win-2022-std-iso --size=120Gi --image-path=win22-std.iso --storage-class=datavg-thin-pool --uploadproxy-url=https://10.49.172.185:31876/ --insecure...