Promote CoreDNS v1.7.0

[rajansandeep]

No description provided.

[johnbelamaric]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: johnbelamaric, rajansandeep

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-coredns/OWNERS [johnbelamaric,rajansandeep]

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

[stp-ip]

Note: Vanity Domain Flip hasn't happened yet (tracked in kubernetes/release#270) and therefore without the legacy way this won't show up on k8s.gcr.io for a few more weeks most likely. The staging image should work so.

[rajansandeep]

@stp-ip @johnbelamaric In that case, can CoreDNS 1.7.0 be promoted to k8s.gcr.io manually?
We plan to include it for k8s 1.19

[stp-ip]

@thockin can you push v1.7.0 the legacy way. Already in the staging repo.
Reference to the last "manual" push: kubernetes/kubernetes#88343

[stp-ip]

/assign @thockin

[thockin]

I don't see this tag in the new repo either - does it actually exist?

[thockin]

e.g. gcr.io/k8s-staging-coredns/coredns:v1.7.0 and us.gcr.io/k8s-artifacts-prod/coredns/coredns:v1.7.0 should exist.

@listx

[listx]

I see in the logs for the promoter that the image (exact sha 73ca82b4ce829766d4f1f10947c3a338888f876fbed0540dc849c89ff256e90c asked-for in the manifest) was not found in the staging repo:

E0629 15:33:03.177923      12 inventory.go:482] edge {{gcr.io/k8s-staging-coredns   true} {coredns v1.7.0} sha256:73ca82b4ce829766d4f1f10947c3a338888f876fbed0540dc849c89ff256e90c {asia.gcr.io/k8s-artifacts-prod/coredns k8s-infra-gcr-promoter@k8s-artifacts-prod.iam.gserviceaccount.com  false} {coredns v1.7.0}}: skipping gcr.io/k8s-staging-coredns/  coredns@sha256:73ca82b4ce829766d4f1f10947c3a338888f876fbed0540dc849c89ff256e90c because it is _LOST_ (can't find it in src registry!)

[thockin]

Sandeep, can you please push this to the staging repo, so promoter can handle it?

…

On Mon, Jun 29, 2020 at 12:50 PM Linus Arver ***@***.***> wrote: I see in the logs for the promoter that the image (exact sha 73ca82b4ce829766d4f1f10947c3a338888f876fbed0540dc849c89ff256e90c asked-for in the manifest) was not found in the staging repo: E0629 15:33:03.177923 12 inventory.go:482] edge {{gcr.io/k8s-staging-coredns true} {coredns v1.7.0} sha256:73ca82b4ce829766d4f1f10947c3a338888f876fbed0540dc849c89ff256e90c {asia.gcr.io/k8s-artifacts-prod/coredns ***@***.*** false} {coredns v1.7.0}}: skipping gcr.io/k8s-staging-coredns/ ***@***.***:73ca82b4ce829766d4f1f10947c3a338888f876fbed0540dc849c89ff256e90c because it is _LOST_ (can't find it in src registry!) — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#976 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABKWAVCKYHK2IQZ2LGUYVGDRZDV7DANCNFSM4OE2N2CA> .

[rajansandeep]

The image is now available, http://gcr.io/k8s-staging-coredns/coredns:1.7.0
thank you @stp-ip for pushing it.

[stp-ip]

sidenote: on the tag
"1.7.0" is used in staging and the legacy process
"v1.7.0" is used with the promoted images to make them more consistent with the other promoted images.