Image promotion for kube-state-metrics v2.8.2

[mrueg]

@rexagod @dgrisonnet @fpetkovski

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: mrueg / name: Manuel Rüger (5acb759)

[mrueg]

/hold

Please lgtm/approve and let me cancel the hold on release day tomorrow.

[dgrisonnet]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dgrisonnet, mrueg

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:

• k8s.gcr.io/images/k8s-staging-kube-state-metrics/OWNERS [dgrisonnet,mrueg]

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

[BenTheElder]

Hey, you'll have to move this to registry.k8s.io/, sorry we're working on kubernetes/enhancements#3720 ref #4934 kubernetes/test-infra#29069

[forcing bot to process this, will reopen immediately]
/close

[k8s-ci-robot]

@BenTheElder: Closed this PR.

In response to this:

Hey, you'll have to move this to registry.k8s.io/, sorry we're working on kubernetes/enhancements#3720 ref #4934 kubernetes/test-infra#29069

[forcing bot to process this, will reopen immediately]
/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.

[BenTheElder]

/reopen

[k8s-ci-robot]

@BenTheElder: Reopened this PR.

In response to this:

/reopen

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.

[k8s-ci-robot]

@mrueg: Adding label: do-not-merge/blocked-paths because PR changes a protected file.

Reasons for blocking this PR:

[k8s.gcr.io Image registry is frozen from April 2023. Please update the manifests in registry.k8s.io folder instead]

• k8s.gcr.io/images/k8s-staging-kube-state-metrics/images.yaml

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.

[mrueg]

@BenTheElder since we would like to release tomorrow and the k8s.gcr.io freeze date is in 2 weeks, can we still process this one?

[BenTheElder]

@BenTheElder since we would like to release tomorrow and the k8s.gcr.io freeze date is in 2 weeks, can we still process this one?

#4934 just moved the configurations from k8s.gcr.io/ to registry.k8s.io/ folder

If you update this PR to move identically you're good to go. But no files will be under k8s.gcr.io/ anymore

That's just a rename to clarify things as part of the freeze, it's not strictly coupled to which registries the images wind up in.

However: Please DO NOT tell people to pull your new image from k8s.gcr.io even if it winds up available there. k8s.gcr.io is deprecated and https://registry.k8s.io is the way forward for the project. We have a tracking issue to ensure all subproject references get updated independent of the freeze on GCR #4738

[BenTheElder]

more specifically: rebase or recreate this diff against registry.k8s.io/images/k8s-staging-kube-state-metrics/images.yaml and the bot will lift the do-not-merged/blocked-paths label.

the same tooling will copy the images to production, and they'll be at pullable at registry.k8s.io/$image:$tag (as they also would have been before moving the source directory here)