Skip to content

Commit 755c9c8

Browse files
stevsmitSteven Smith
andauthored
Adds proxy cache limitation (#1374)
Co-authored-by: Steven Smith <[email protected]>
1 parent ecceb16 commit 755c9c8

File tree

2 files changed

+5
-3
lines changed

2 files changed

+5
-3
lines changed

modules/proxy-cache-limitations.adoc

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,4 +5,6 @@ Proxy caching with {productname} has the following limitations:
55

66
* Your proxy cache must have a size limit of greater than, or equal to, the image you want to cache. For example, if your proxy cache organization has a maximum size of 500 MB, and the image a user wants to pull is 700 MB, the image will be cached and will overflow beyond the configured limit.
77

8-
* Cached images must have the same properties that images on a Quay repository must have.
8+
* Cached images must have the same properties that images on a Quay repository must have.
9+
10+
* Anonymous users cannot pull images through a proxy cache if the image has not been previously cached. This operation requires the creation of a new repository within the proxy organization to store the cached image, and anonymous users do not have the necessary permissions to create repositories.

modules/proxy-cache-procedure.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,9 +23,9 @@ The following procedure describes how you can use {productname} to proxy a remot
2323
By adding a namespace to the *Remote Registry*, for example, `quay.io/<namespace>`, users in your organization will only be able to proxy from that namespace.
2424
====
2525

26-
. Optional. In the *Remote Registry username* box, enter the username for authenticating into the remote registry specified in the previous step. For anonymous pulls from the upstream, you can leave this empty. If you do note set a username at the time of creation, you cannot add one without removing the proxy cache and creating a new registry.
26+
. Optional. In the Remote Registry username box, enter the username for authenticating into the remote registry specified in the previous step. If you leave this empty, Quay will attempt to pull content anonymously from the upstream registry.
2727

28-
. Optional. In the *Remote registry password* box, enter the password for authenticating into the remote registry. For anonymous pulls from the upstream, you can leave this empty. If you do note set a username at the time of creation, you cannot add one without removing the proxy cache and creating a new registry.
28+
. Optional. In the Remote registry password box, enter the password for authenticating into the remote registry. If you leave this empty, Quay will attempt to pull content anonymously from the upstream registry.
2929

3030
. Optional. Set a time in the *Expiration* field.
3131
+

0 commit comments

Comments
 (0)