-
Notifications
You must be signed in to change notification settings - Fork 254
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DataImportCron does not support images with sha256 digest #2689
Comments
Ignore my previous comment, didn't notice the cron was applied correctly
|
@arnongilboa Please provide some steps for using the manual annotation to specify the sha explicitly (disabling the schedule). |
@kvaps You currently have no way to disable the the initial poller Job, or the poller CronJob. Validation webhook checks it's a legal cron schedule. You can set a once-a-year schedule (e.g. "0 0 1 1 *") but it won't help you with the initial one. If we must get rid of the poller we should add a support for a "disable" schedule value. However, if the poller simply fails in your scenario due to secrets etc, and you know when the source image is updated and can provide its sha256 digest, you can simply do the poller work and annotate the DataImportCron with the new sha256 digest, as we do in the functests, or manually:
|
CDIv1.59 I continue playing with DataImportCrons:
I created resource:
CDI generated DataVolume with duplicated digests in url:
log of importer pod:
The text was updated successfully, but these errors were encountered: