Add support for k8s-stable4 version marker

[xmudrii]

What would you like to be added:

We should add support for the k8s-stable4 version marker because it might happen that we support 4 branches in parallel.

(Part of #850.)

Why is this needed:

We had a problem that we supported 1.25, 1.24, 1.23, and 1.22 at the same time. In this case, both ci-kubernetes-build-1.23 and ci-kubernetes-build-1.22 pointed to the k8s-stable3 version marker. This might cause issues with tests or produce test results that are not reliable because the same k8s-stable3 version marker is getting changed by two different jobs for two different release branches.

We mitigated this manually by adding the k8s-stable4 version marker in kubernetes/test-infra#27945, but we'll mostly like end up with the same problem again once 1.26 is out. That being said, we might need to modify config-rotator and update docs.

[saschagrunert]

Yep, docs have to be updated for that as well:

• https://github.com/kubernetes/community/blob/master/contributors/devel/sig-release/kubernetes-versions.md
• https://github.com/kubernetes/sig-release/blob/master/release-team/role-handbooks/ci-signal/upgrade-job-versions.md

[xmudrii]

Alternatively, considering that those k8s-stable version markers are deprecated, we should check if those jobs can switch to the new release markers.

[justaugustus]

(transferred this to k/sig-release)

[justaugustus]

/assign @xmudrii

[xmudrii]

@justaugustus I would consider this done since we support the stable4 marker and there are jobs using it. Do you think it's okay to close this issue or is there anything I forgot about?

[justaugustus]

Do you think it's okay to close this issue or is there anything I forgot about?

Let's wait until kubernetes/test-infra#28119 merges. :)

[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

[xmudrii]

/remove-lifecycle stale

[xmudrii]

We have full support for the stable4 version marker with kubernetes/test-infra#29098. It's also documented here: https://github.com/kubernetes/community/blob/ad1bca23543ed0adc27c2ce7935454b0b7be9b12/contributors/devel/sig-release/kubernetes-versions.md?plain=1#L331

With that, I'm going to close this issue.
/close

[k8s-ci-robot]

@xmudrii: Closing this issue.

In response to this:

We have full support for the stable4 version marker with kubernetes/test-infra#29098. It's also documented here: https://github.com/kubernetes/community/blob/ad1bca23543ed0adc27c2ce7935454b0b7be9b12/contributors/devel/sig-release/kubernetes-versions.md?plain=1#L331

With that, I'm going to close this issue.
/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.