sig-testing: support auto-tag and auto-bump for test images

[chewong]

I forget how this works but technically we can't use 2.30 until it's been promoted. Usually there's a followup PR that updates test/images/manifest once promotion has occurred. Is that the more appropriate PR to make this change?

The two-step image promotion dance and fixed/hardcoded version approach used by e2e test images could really stand to be revisited. Not suggesting we try to do it in v1.21 just more thinking out loud. Auto-tagging with date+gitsha is an approach that's worked well for other images in this project AFAIK.

Originally posted by @spiffxp in #99860 (comment)

[chewong]

/sig testing

[BenTheElder]

I think auto tag is a good idea. I don't think we're ready for auto-promote yet which would block automatically using new tags.

[BenTheElder]

This should probably be brought up somewhere with more visibility to see if anyone has concerns with date-sha, but otherwise I think this is
/triage accepted

[BenTheElder]

raised in #sig-testing slack to see if anyone else has input

[spiffxp]

/milestone v1.23
I think this worth considering now that we've consolidated most images to staging repos

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[NilimaC04]

Hi 👋 I'm the bug triage shadow for release 1.23.
There hasn't been any activity on this issue for a couple of months now. Just want to make sure this issue is still on track for the 1.23?

[BenTheElder]

I don't think this is happening in 1.23 at least. I'm not aware of anyone taking this up.
/milestone clear

[NilimaC04]

Thanks for the update @BenTheElder! Can we plan to do this in v1.24?

[BenTheElder]

I don't know of anyone planning to work on this currently, so I don't think we can plan on any particular milestone.

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[BenTheElder]

/lifecycle frozen

[k8s-triage-robot]

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

[k8s-ci-robot]

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.