Revert "Promote coredns to v1.13.1 and v1.13.0"

[pacoxu]

Reverts #8652

only revert v1.13.1 as the image promotion failed.

[root@paco ~]# nerdctl pull registry.k8s.io/coredns/coredns:v1.13.1
registry.k8s.io/coredns/coredns:v1.13.1: resolving      |--------------------------------------| 
elapsed: 0.9 s                           total:   0.0 B (0.0 B/s)                                         
INFO[0001] trying next host - response was http.StatusNotFound  host=registry.k8s.io
FATA[0001] failed to resolve reference "registry.k8s.io/coredns/coredns:v1.13.1": registry.k8s.io/coredns/coredns:v1.13.1: not found 
[root@paco ~]# nerdctl pull registry.k8s.io/coredns/coredns:v1.13.0
registry.k8s.io/coredns/coredns:v1.13.0:                                          resolved       |++++++++++++++++++++++++++++++++++++++| 
index-sha256:da282c1983a1a330240e6e84eaec9b6120b0de0e7e29e92c44a6acd25f9e0238:    exists         |++++++++++++++++++++++++++++++++++++++| 
manifest-sha256:ec590162a6ca314b1e760f6591b26050267ae6d94d67e1926b44994fdad81200: exists         |++++++++++++++++++++++++++++++++++++++| 
config-sha256:6eaf5c6df60ede781f372972c43683948400ae5205de4d17cfc2c92914bc7766:   exists         |++++++++++++++++++++++++++++++++++++++| 
elapsed: 1.2 s     

[pacoxu]

/cc @stp-ip @yashsingh74

[yashsingh74]

/lgtm

[yashsingh74]

@pacoxu will you be creating the separate PR for 1.13.1 ??

[ameukam]

FYI, this will not remove the tag in the prod registry as we don't delete anything in prod. Promoting the same tag with a different SHA will break the promotion process.

[pacoxu]

FYI, this will not remove the tag in the prod registry as we don't delete anything in prod. Promoting the same tag with a different SHA will break the promotion process.

@ameukam The v1.13.1 image was not promoted due to that staging image was not ready when last PR was merged.

• In that PR, it also include the v1.13.0 image, which was promoted successfully.

What I want do here it to revert the v1.13.1 image promotion here and then I will submit a PR to promote it again as the staging image should be ready now. Will this process work?

Or if the promotion can be done by some re-triggering(I think I don't have the permission).

[pacoxu]

Some context in kubernetes/kubernetes#133968 (comment).

[ameukam]

FYI, this will not remove the tag in the prod registry as we don't delete anything in prod. Promoting the same tag with a different SHA will break the promotion process.

@ameukam The v1.13.1 image was not promoted due to that staging image was not ready when last PR was merged.

* In that PR, it also include the v1.13.0 image, which was promoted successfully.

What I want do here it to revert the v1.13.1 image promotion here and then I will submit a PR to promote it again as the staging image should be ready now. Will this process work?

Or if the promotion can be done by some re-triggering(I think I don't have the permission).

Thanks for the clarity. I should be fine to revert this.

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ameukam, pacoxu

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:

• registry.k8s.io/images/k8s-staging-coredns/OWNERS [ameukam]

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