User Harbor ourselves

[Vad1mo]

Use of our Harbor registry to distribute our own container images. We should be the first to adopt our own technology. If we are not willing to utilize our own application for day-to-date use, don't expect others to do so.

[slushysnowman]

I like the idea, but there probably need to be mitigating measures taken to ensure that if this Harbor instance goes down, that it can come back up right - if it's referencing itself as source of images, there are potential issues.

We're in the process of doing something similar at the moment, we're going to use our internal Harbor to store all our platform images, but we're going build in an automatic failover mechanism to pull from (in our case) ACR in the case where Harbor is down.

Maybe something to include here in some way/shape/form?

[Vad1mo]

I like the idea, but there probably need to be mitigating measures taken to ensure that if this Harbor instance goes down, that it can come back up right - if it's referencing itself as source of images, there are potential issues.

We're in the process of doing something similar at the moment, we're going to use our internal Harbor to store all our platform images, but we're going build in an automatic failover mechanism to pull from (in our case) ACR in the case where Harbor is down.

Maybe something to include here in some way/shape/form?

Yeah it makes sense to replicate to other registries eg. docker hub, or ghcr in case the outage takes to longer to recover.

[Vad1mo]

The current registry is available in https://registry.goharbor.io, you can already use it to pull Harbor images. We currently replicate images from Docker Hub.

[wy65701436]

Can we introduce Phase 0?

I believe we should aim for a graceful migration and use the test assets as a pilot to validate the stability and availability of the system for a period of time.