Closed jandubois closed 4 years ago
viccuad
commented
4 years ago splatform/catapult is being built on concourse.suse.de, from https://github.com/SUSE/cloudfoundry/blob/master/ci/pipelines/catapult/pipeline.yml. This may be the case for all the splatform org images.
jandubois
commented
4 years ago I've moved the the 2 images used by the pipeline to ghcr.io/jandubois:
resource/github-status
splatform/github-pr-resourceEspecially the github-pr-resource is downloaded way more often than I expected.
Anyways, we need to create a Github organization that can become the owner of all these images; they should not be stored under a personal account.
The name should not mention concourse but be generic enough to include also all the images for bosh releases, for stemcells, and for the quarks operator.
viccuad
commented
4 years ago @jandubois honest thanks for moving the images; that should have been me, and I was blocking CI.
@viovanov could we create the GH org now? or should we reuse cloudfoundry-incubator as quarks does? In the second case, we would need credentials for it.
Once we have a target org, we can change the target of suse-buildpacks-ci, eirinix, and the rest of imagelist.txt to also publish there.
viovanov
commented
4 years ago @viccuad please use the incubator org
jandubois
commented
4 years ago I've added some comments on #1581 about images for autoscaler and eirini.
viccuad
commented
4 years ago Prereequisites:
For all images to migrate:
Possible incomplete list of images to push to ghcr.io:
splatform/github-pr-resource
resource/github-status
Opened https://github.com/cloudfoundry-incubator/kubecf/pull/1585docker.io/cfcontainerization/coredns
https://build.opensuse.org/package/show/Cloud:Platform:quarks:images/coredns
ghcr.io/cfcontainerizationbot/kubecf-apps-dns
ghcr.io/cfcontainerizationbot/kubecf-kubectl
mook-as
commented
4 years ago With #1581 merged, the current list of images I have (from an amalgamation of two clusters, one diego and one eirini, both in the middle of 🐱), including any system pods:
The only relevant ones are:
cfcontainerization/cf-operator:v6.1.17-0.gec409fd7
cfcontainerization/coredns:0.1.0-1.6.7-bp152.1.19
cfcontainerization/quarks-job:v1.0.206
cfcontainerization/quarks-secret:v1.0.744
docker.io/bitnami/external-dns:0.7.4-debian-10-r41
docker.io/bitnami/nginx-ingress-controller:0.40.2-debian-10-r27
docker.io/bitnami/nginx:1.19.4-debian-10-r4This boils down to quarks (we'll need to consumer a newer release) and the ingress chart.
viccuad
commented
4 years ago The following
docker.io/bitnami/external-dns:0.7.4-debian-10-r41
docker.io/bitnami/nginx-ingress-controller:0.40.2-debian-10-r27
docker.io/bitnami/nginx:1.19.4-debian-10-r4come from https://github.com/SUSE/cap-terraform/tree/cap-ci and its upstsream helm charts being installed in the terraform scripts. Those charts get installed on the Terraform call, so it happens directly on the public cloud provider, hitting their container mirrors. I think it's safe to ignore them.
From the quarks ones:
cfcontainerization/cf-operator:v6.1.17-0.gec409fd7
cfcontainerization/coredns:0.1.0-1.6.7-bp152.1.19
cfcontainerization/quarks-job:v1.0.206
cfcontainerization/quarks-secret:v1.0.744Only coredns is not changed yet. The image comes from registry.opensuse.org, https://build.opensuse.org/package/show/Cloud:Platform:quarks:images/coredns, and is pushed here: https://concourse.suse.de/teams/main/pipelines/obs-to-dockerhub-pusher.
Tim and I updated that pipeline and renamed it, now it is in https://concourse.suse.de/teams/main/pipelines/obs-to-ghcr-pusher, and coredns images are being published.
I will open a PR against quarks and link it here.
viccuad
commented
4 years ago I suppose we just need to consume a new quarks-operator release now, to close this card.
mook-as
commented
4 years ago Added https://github.com/SUSE/cap-terraform/pull/102 to make cap-terraform consume the upstream ingress-nginx chart instead of the bitnami one; that one uses gcr.io, so it should work around any potential Docker Hub quota issues.
The last few PR builds failed to report status back to Github:
We should move all images used by Concourse to the Github registry instead. The above image is from https://github.com/colstrom/concourse-github-status
But we are still pulling many more images from Dockerhub, at the very least: