Quay self-hosted Registry Caching

[jonas-budde]

What is the problem you're trying to solve At the moment I want to connect a self-hosted quay registry from a contractor to our azure container registry. This isn't possible, because the contractor is self-hosting his quay registry. This way we could also cache images from a self-hosted quay registry.

Describe the solution you'd like I should be possible to create a credential set with a custom login server and a cache rule with a custom URL to a (self-hosted) quay registry.

Additional context Documentation for the current state of this feature

[jonas-budde]

Hello @JXavierMSFT, are there any updates on this?

[PatrickSpies]

Same would be helpful for (selfhosted) gitlab-registry..

[JXavierMSFT]

Hey @jonas-budde and @PatrickSpies,

This functionality is on our roadmap. I will update this thread when I have a solid timeline on when we will deliver it.

[joshua-hancox]

Another thumbs up for this, would like to cache artifacts from our supplier (F5) private repo that requires authentication.

Is there any update on progress/timelines since Nov?

[toddysm]

Please follow the parent issue for progress.