Using Harbor as the source for Azure/AWS pull through cache.

[ncrmro]

I understand this is not an issue with Harbor per say but wondering if there is any guidance or work arounds currently.

Context being we distribute images and some of our private install clients would like to pull our images into their registries.

➜  ~ aws --profile us-prod ecr create-pull-through-cache-rule \
     --ecr-repository-prefix harbor \
     --upstream-registry-url harbor.example.com \
     --region us-east-1

An error occurred (UnsupportedUpstreamRegistryException) when calling the CreatePullThroughCacheRule operation: The upstream registry URL harbor.example.com is invalid. Specify a valid upstream registry URL and try again

Azure ACR has an issue for this and mentioned it was in the works but it's closed because it's stale.

➜  ~ az acr cache create -r example -n example-harbor -s harbor.example.com -t example-images
(UpstreamNotSupported) Unsupported upstream or login server 'harbor.example.com' provided. Supported upstreams or login servers are: docker.io, mcr.microsoft.com, quay.io, public.ecr.aws, ghcr.io, nvcr.io, registry.k8s.io, gcr.io.
Code: UpstreamNotSupported
Message: Unsupported upstream or login server 'harbor.example.com' provided. Supported upstreams or login servers are: docker.io, mcr.microsoft.com, quay.io, public.ecr.aws, ghcr.io, nvcr.io, registry.k8s.io, gcr.io.

[wy65701436]

Just have a quick through about https://docs.aws.amazon.com/cli/latest/reference/ecr/create-pull-through-cache-rule.html, it seems that harbor is not supported as the source for the pull through cache rule.

You should file an feature request on the ACR.

And can you share the use case why you choose the harbor as the upstream registry when issue an pull image request to ACR?

[github-actions]

This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days.

[github-actions]

This issue was closed because it has been stalled for 30 days with no activity. If this issue is still relevant, please re-open a new issue.