shared-images-controller: evaluate whether we should cache kubevirtci images for the release branches

[dhiller]

ATM we only cache the kubevirtci images used in main branch of kubevirt/kubevirt.

We should evaluate whether it makes sense to also cache the images from the release branches.

I.e. common-instancetypes also uses kubevirtci and references the version from the kubevirt/kubevirt release branch.

[dhiller]

FYI @0xFelix @brianmcarey

[kubevirt-bot]

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

[kubevirt-bot]

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

[kubevirt-bot]

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

/close

[kubevirt-bot]

@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/test-infra repository.

[dhiller]

@brianmcarey I think this has proven to not be necessary, so we can keep this closed. WDYT?

[0xFelix]

@dhiller I did not stumble over this again, let's keep it closed for now.