reconcile kubernetes/kubernetes stableN version markers

[spiffxp]

Addresses #19922 (comment)

When the gs://k8s-release-dev/ci/k8s-stableN.txt' version markers were rolled forward, the equivalents in gs://kubernetes-release-dev` were missed.

The config for auto-generated release jobs in releng/ was also missed, so some stable1 jobs were pointed at v1.19 (two releases ago instead of 1)

No longer WIP now that:

• I haven't verified whether the stableN job names match up properly, and confirmed everything on a given release-1.y-blocking testgrid dashboard actually uses release-1.y lgtm
• This contains commits from Log or enforce kubernetes jobs pull from k8s-infra buckets #20885, I'll rebase once that merges rebased

What I consider out of scope for this PR, but am open to for followup:

• replace 'stableN' with '1-y' in job names (we lose job history in e.g. testgrid for a bit, but we're early enough in release cycle to make this change IMO)
• replace uses of '--extract=ci/k8s-stableN' with more concrete version markers

I'm less certain we can drop populating the ci/k8s-stableN version markers without a deprecation window

[spiffxp]

Needed to rebase due to #20880 merging

[cpanato]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cpanato, spiffxp

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• config/jobs/kubernetes/generated/OWNERS [spiffxp]
• config/jobs/kubernetes/sig-release/OWNERS [cpanato,spiffxp]
• config/testgrids/kubernetes/sig-release/OWNERS [cpanato,spiffxp]
• releng/OWNERS [cpanato,spiffxp]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

@spiffxp: Updated the job-config configmap in namespace default at cluster test-infra-trusted using the following files:

• key generated.yaml using file config/jobs/kubernetes/generated/generated.yaml
• key 1.18.yaml using file config/jobs/kubernetes/sig-release/release-branch-jobs/1.18.yaml
• key 1.19.yaml using file config/jobs/kubernetes/sig-release/release-branch-jobs/1.19.yaml
• key 1.20.yaml using file config/jobs/kubernetes/sig-release/release-branch-jobs/1.20.yaml

In response to this:

Addresses #19922 (comment)

When the gs://k8s-release-dev/ci/k8s-stableN.txt' version markers were rolled forward, the equivalents in gs://kubernetes-release-dev` were missed.

The config for auto-generated release jobs in releng/ was also missed, so some stable1 jobs were pointed at v1.19 (two releases ago instead of 1)

No longer WIP now that:

• I haven't verified whether the stableN job names match up properly, and confirmed everything on a given release-1.y-blocking testgrid dashboard actually uses release-1.y lgtm
• This contains commits from Log or enforce kubernetes jobs pull from k8s-infra buckets #20885, I'll rebase once that merges rebased

What I consider out of scope for this PR, but am open to for followup:

• replace 'stableN' with '1-y' in job names (we lose job history in e.g. testgrid for a bit, but we're early enough in release cycle to make this change IMO)
• replace uses of '--extract=ci/k8s-stableN' with more concrete version markers

I'm less certain we can drop populating the ci/k8s-stableN version markers without a deprecation window

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.