Quay self-hosted Registry Caching #769
Assignees
Labels
feature-artifact-sync
Issues related to Artifact Sync feature
feature-request
Issues that request new features
triaged
Use after the issue is triaged
Comments
|
Hello @JXavierMSFT, are there any updates on this? |
|
Same would be helpful for (selfhosted) gitlab-registry.. |
|
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. |
toddysm
added
triaged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
The text was updated successfully, but these errors were encountered: