ExternalDNS: promote v0.5.18

[linki]

This promotes v0.5.18 from staging to production.

I wonder if the docker image described by the sha256 must already be tagged v0.5.18 in the staging registry or if that is taken care of when promoting it.

Background: We didn't manage to push to the staging repository with our desired tags yet. They still are prefixed with the date, see here.

Anyway, we figured it might be worth a try 😃

[linki]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: linki

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-external-dns/OWNERS [linki]

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

[linki]

/lgtm

[k8s-ci-robot]

@linki: you cannot LGTM your own PR.

In response to this:

/lgtm

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.

[Raffo]

@linki Happy to LGTM this, but in general can you provide some guidelines for releasing ExternalDNS in the ExternalDNS repo?

[Raffo]

/lgtm

[linki]

Thanks @Raffo. You're right, we should document that once it's working. I created an issue: kubernetes-sigs/external-dns#1371

[linki]

To answer the above question: The image doesn't need to be tagged in staging. The logic of the YAML in here is: take the image with the sha256, mirror it to production, and tag it with the tag.