Use porscheinformatik-images because zalando/teapot isn't built timely

[jgrumboe]

I would like to change the tutorial for openshift-route source to use images from docker.io/porscheinformatik/external-dns, because I currently don't know when the images for registry.opensource.zalan.do/teapot/external-dns are built.

Furthermore it would be good to have images in an "official" kubernetes-sigs registry, if such exists.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: jgrumboe
To complete the pull request process, please assign hjacobs
You can assign the PR to them by writing /assign @hjacobs in a comment when ready.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[jgrumboe]

/assign @njuettner

[jgrumboe]

/unassign @njuettner
/assign @hjacobs

[njuettner]

@jgrumboe thanks for your PR, we probably forgot to update the how to docs for each provider but we moved away from this registry. We use now the official registry for all kubernetes sigs projects see in our releases.

Here are latest images for each region:

docker run asia.gcr.io/k8s-artifacts-prod/external-dns/external-dns:v0.7.1 --help
docker run eu.gcr.io/k8s-artifacts-prod/external-dns/external-dns:v0.7.1 --help
docker run us.gcr.io/k8s-artifacts-prod/external-dns/external-dns:v0.7.1 --help

[jgrumboe]

@njuettner Do I understand it correctly that images are only built after releasing a new version, so there's no :latest tag after each merged commit?
If so, I would like to stick with porscheinformatik images for the openshift tutorial until a new version is released.

[Raffo]

I'd love to get us to a point in which we own nightly builds rather than having a single organization owning the release process. Being the release process for the official builds a bit of a pain, we should keep the ones mentioned by @njuettner for stable release and something else for nightly builds. For that reason, I'm against this change and rather for fixing the underlying problem.

[seanmalloy]

It looks like each commit to master gets built and pushed to the staging registry for external-dns.

Here is the command to list all of the tags in the staging registry. These would be equivalent-ish to night builds and not stable releases.

gcloud container images list-tags gcr.io/k8s-staging-external-dns/external-dns

I hope that helps.

[Raffo]

Oh that's sweet I didn't even know that! I'll keep this issue around to document that behavior, close it when done.

[njuettner]

@njuettner Do I understand it correctly that images are only built after releasing a new version, so there's no :latest tag after each merged commit?
If so, I would like to stick with porscheinformatik images for the openshift tutorial until a new version is released.

Correct 🙂 , but as @seanmalloy pointed out you can also use the staging external-dns source, which will create for each PR an image which you could use as a kind of night build.

Or you can use this link (but this needs probably an google account):
https://console.cloud.google.com/gcr/images/k8s-staging-external-dns/GLOBAL/external-dns?gcrImageListsize=30

[njuettner]

Please change it to the official registry as I mentioned in my comment 🙂

[jgrumboe]

@njuettner I understand. But wouldn't the kubernetes-staging image be better, since as long as no new release is released new users would try an image which doesn't reflect the new capability.

[jgrumboe]

/hold
@Raffo @njuettner I will wait for the next release and update the image link to eu.gcr.io/k8s-artifacts-prod/external-dns/external-dns:WHAT-EVER-NEW-VERSION.
Wouldn't it be great to have a "latest" tag? (https://console.cloud.google.com/gcr/images/k8s-artifacts-prod/EU/external-dns/external-dns?gcrImageListsize=30)
"latest" would make sense for the tutorials.