config forking should ensure image tag is valid

[BenTheElder]

What happened:

#34651 (comment) / #34672

because we introduced the 1.33 image variants a few days ago, but haven't bumped the jobs to new images, the mutated image tag from the existing jobs to -1.33 was not available, causing jobs to fail

What you expected to happen:

We should probably detect and handle this. It might make sense to just adopt the latest available on the new branch.

How to reproduce it (as minimally and precisely as possible):
n/a

Please provide links to example occurrences, if any:

n/a

Anything else we need to know?:

Low prio, something to consider before ~4 months from now.

/sig release testing

[BenTheElder]

#34592 is the current automated image bump PR

we very intentionally don't merge these constantly, as we rarely need anything from these updates, but they carry a broad risk and may need reverting

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[BenTheElder]

/remove-lifecycle stale
/lifecycle frozen
same issue in 1.34
https://kubernetes.slack.com/archives/CN0K3TE2C/p1754679388706789

[saschagrunert]

/assign