[WIP] CNV-23832: Apply StorageClass from Template's boot source

[avivtur]

📝 Description

When there's no StorageClass defined in the template or default StorageClass in the cluster, the CDI clone process can't determine which StorageClass to use and the DataVolume does not create its PersistentVolumeClaim.
If a template has an available boot source, we should apply the boot source's StorageClass if exist to allow VM to be created.

Note: This applies to the quick create flow for now, as we some issue with customize flow:

🎥 Demo

Before:

cant-clone.mp4

After:

clone-from-ds-pvc.mp4

[openshift-ci-robot]

@avivtur: This pull request references CNV-23832 which is a valid jira issue.

In response to this:

📝 Description

When there's no StorageClass defined in the template or default StorageClass in the cluster, the CDI clone process can't determine which StorageClass to use and the DataVolume does not create its PersistentVolumeClaim.
If a template has an available boot source, we should apply the boot source's StorageClass if exist to allow VM to be created.

Note: This applies to the quick create flow for now, as

🎥 Demo

Before:

cant-clone.mp4

After:

clone-from-ds-pvc.mp4

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: avivtur

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [avivtur]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci-robot]

@avivtur: This pull request references CNV-23832 which is a valid jira issue.

In response to this:

📝 Description

When there's no StorageClass defined in the template or default StorageClass in the cluster, the CDI clone process can't determine which StorageClass to use and the DataVolume does not create its PersistentVolumeClaim.
If a template has an available boot source, we should apply the boot source's StorageClass if exist to allow VM to be created.

Note: This applies to the quick create flow for now, as we some issue with customize flow:

🎥 Demo

Before:

cant-clone.mp4

After:

clone-from-ds-pvc.mp4

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[metalice]

this is a partial fix? not fixing customize flow ?

[avivtur]

@metalice Currently this PR is using the first SC it finds from the list (as the 4.15 cluster has volume snapshots and not PVC) we should figure out a way to get the SC from the boot source or simply use the first one as I do currently.
BTW this functionality will exist only in UI