Reduce External Registry Pulls with Harbor Proxy Cache
Use Harbor proxy cache as a pull-through mirror for Docker Hub to reduce external pulls and protect CI from rate limits without changing client commands.
Loading…
ReadMeFeed / Community knowledge
#proxy-cache
Real questions. Useful conversations. Find the people who know your stack.
harborNGINX Reverse‑Proxy Caching: How to Store, Serve, and Purge Upstream Responses
NGINX’s proxy_cache turns the reverse proxy into a disk‑backed cache. Learn how to define the cache zone, control TTLs, verify hits, and manage disk space and purging in this practical guide.
nginxCaching at the Edge of Your App: A Practical Look at NGINX proxy_cache
NGINX can absorb most of your read traffic before it reaches the app tier. A practical guide to proxy_cache: a working configuration, stampede protection, verification, and the staleness trade-offs.
Using Harbor Proxy Cache to Bypass Docker Hub Rate Limits
When CI/CD or Kubernetes pulls hit Docker Hub rate limits, a Harbor proxy cache can solve the problem. This guide walks through creating a cache project, pulling images, and verifying the cache works.
Harbor Proxy Cache vs Replication: How to Choose for Upstream Images
Proxy cache and replication both make upstream images available in Harbor, but they fail differently. Compare constraints, storage, and validation steps before choosing.
Preventing 502 Errors with NGINX proxy_cache_use_stale
Learn how to use NGINX's proxy_cache_use_stale directive to serve cached content during backend failures, eliminating 502 errors during maintenance windows.
proxy_cache_use_stale limits for upstream errors and expired content
Designing a caching layer with nginx proxy_cache requires clarity on when stale responses may be returned when the origin is unavailable. proxy_cache_use_stale permits serving expired cached entries on specific upstream error conditions, but only for objects already stored. The maximum age of usable stale data is bounded by proxy_cache_valid and optionally p
Change in proxy_cache_use_stale updating behavior with proxy_cache_background_update enabled from nginx 1.19.0 onward
When both proxy_cache_use_stale updating and proxy_cache_background_update are enabled, nginx must decide whether to return the existing stale cache entry immediately or to wait for the asynchronous background fetch to finish before responding. The documentation notes that the stale response is served only if the request arrives before the background update
Stale Cache Update Timing with proxy_cache_background_update
The goal is to determine when nginx replaces a stale cache entry after a background refresh initiated by proxy_cache_background_update . Documentation specifies that stale content can be served while a background subrequest updates the cache, but it does not clarify whether the updated object overwrites the stale entry immediately upon completion of the back