Automatize container hashes update about kubevirtci

[qinqon]

@slintes there it is

[slintes]

Hey @qinqon, thanks for that proposal. We need more automation for this for sure!
About your suggestion: using a moving stable tag is not an ideal solution, because that can result in using old cached images. We would like to stick with shasums because of that.
My suggestion would be to track all shasums in 1 parsable text file, and get them from there where needed.
A postsubmit job which rebuilds and pushes all needed images sounds great. It only needs to update that shasum file as well then.
Let's use this issue to elaborate more on this.

[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.