Closed kvaps closed 10 months ago
Ahh, it creates cronjob in CDI namespace, sorry I was confused by missing events for DataImportCron object. I think we should add the event that import has been started
And it seems that DataImportCron does not supporting pullMethod: node
And it seems that DataImportCron does not supporting
pullMethod: node
It should be supported, not sure what goes wrong
certConfigMap: some-certs
Do you really need extra certs using this public quay.io image? Did you also create this ConfigMap?
It should be supported, not sure what goes wrong
Yeah it should work, but it requires me to create secret in both namespaces. Where CDI is running (for cronjob) and where DataVolume is get created (for importer job).
Previously I didn't use any secrets for DataVolumes, because pullMethod: node
allows to use secret directly from CRI.
certConfigMap: some-certs Do you really need extra certs using this public quay.io image? Did you also create this ConfigMap?
Not really, but I need registry with secretRef, which works the similar way
So the point of pullMethod: node
is that you use the node to retrieve the image from the registry, so you don't have to provide a pull secret to the pod. If your node can access the registry, then just setting pullMethod: node
without providing a pull secret should work.
Unfortunately this is not working, since cronjob in cdi namespace also requires this secret.
If I don't use pullMethod: node
, then I have to create even two secrets, one in cdi namespace, second in target namespace
There are two elements to this:
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
/remove-lifecycle stale
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.
What happened:
I just follow doced os-image-poll-and-update.md
What you expected to happen:
DataVolume successfully created
How to reproduce it (as minimally and precisely as possible):
Additional context:
logs:
Environment:
v0.56
v1.26.3
Ubuntu 22.04 LTS
5.15.0-25-generic