CDI dataimporcron is failed with this error Error from server: error when creating "importcrondv.yaml": admission webhook "dataimportcron-validate.cdi.kubevirt.io" denied the request: Missing registry source
Hi Team,
I tried to create Dataimportcron to import qcow2 image from jfrog generic artifactory to create datavolume so that launch kubevirt vm from it but it is failed due to below error. Error message: Error from server: error when creating "importcrondv.yaml": admission webhook "dataimportcron-validate.cdi.kubevirt.io" denied the request: Missing registry source. , Mainfest file:
kind: DataImportCron
metadata:
name: jfrog-demo-image-import-cron
namespace: default
spec:
template:
spec:
source:
http:
url: "http://dev-artifactory.example.com/artifactory/demo-project/linux-8-kube.qcow2"
#pullMethod: node # S3 or GCS
#secretRef: "" # Optional
certConfigMap: "example-cert" # Optional
pvc:
accessModes:
- ReadWriteMany
volumeMode: Block
resources:
requests:
storage: "105Gi"
#storage:
# resources:
# requests:
# storage: 5Gi
# storageClassName: hostpath-provisioner
schedule: "0 20 * * *"
garbageCollect: Outdated
importsToKeep: 2
managedDataSource: jfrog-demo-image-import-cron.
if i used below code i got this error:
code:
source:
registry:
url: "http://dev-artifactory.example.com/artifactory/demo-project/linux-8-kube.qcow2"
#pullMethod: node # S3 or GCS
#secretRef: "" # Optional
certConfigMap: "example-cert" # Optional
Error from server: error when creating "importcrondv.yaml": admission webhook "dataimportcron-validate.cdi.kubevirt.io" denied the request: Illegal registry source URL scheme.
please help me to resolve the issue how to import image from http source for dataimportcron resource.
Hey @poreddiharsha412, currently dataImportCron only supports importing from registry. You can check some examples of how this data source works here. That said, HTTP support for dataImportCron is in the works. The PR still needs some time, but it'll probably be supported in the near future.
@alromeros, Thank you for your response. May i know any ETA for this feature and in which cdi versions it will be available.
In this case due to external factors it's really hard to give an estimated date. I'll update you once the feature is merged. Hope this helps!
Thank you for your update
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
/lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
/close
@kubevirt-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity. Reopen the issue with
/reopen. Mark the issue as fresh with/remove-lifecycle rotten./close
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-sigs/prow repository.