404 Not Found for manifest after upstream update in Harbor proxy cache
Problem Context When an upstream registry updates a mutable tag, Harbor’s proxy cache may still serve a previously cached manifest. The Docker client then receives a 404 Not Found when pulling the new digest, indicating that the proxy cache has not yet been refreshed. Constraints & Uncertainty Proxy cache entries are governed by a configurable TTL, and H
harbor