Repost from ovh/kubernetes channel:
👋 Something is funny with Harbor/Private Registry. Cannot connect (503 Service temporarily unavailable) despite OVH console stating "OK" status.
@mircea.negreanu_gitlab Unfortunatly this problem is not easily solvable.
I'm still investigating on some specific cases, I will probably open a dedicated travaux task...
The 's3aws PathNotFound' is linked to an issue with our backend storage, and we can't change it for now. So we will try to reduce as much as we can the impact and the frequency.
ERROR: Job failed (system failure): failed to pull image "xxxxxx.gra5.container-registry.ovh.net/xxx/xxx:latest" with specified policies [always]: Error response from daemon: Get https://xxxxxx.gra5.container-registry.ovh.net/v2/xxx/xxx/manifests/latest: received unexpected HTTP status: 503 Service Temporarily Unavailable (manager.go:214:0s)
error pulling image configuration: Get "https://storage.GRA.cloud.ovh.net/84bfb275-a86f-4707-802b-4efc5050a519/files/docker/registry/v2/blobs/sha256/20/200117eb6cb0c14ca74b52a5e2daa9f355e6fb811b4cd2d0d54a7a82cb37d820/data?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=xxx%2F20211013%2FGRA%2Fs3%2Faws4_request&X-Amz-Date=20211013T093524Z&X-Amz-Expires=1200&X-Amz-SignedHeaders=host&X-Amz-Signature=sss": read tcp 192.168.50.58:49664->18.104.22.168:443: read: connection reset by pee