Cache Clearance Causing 404 Havoc

[suning-li]

Hello Harbor Team,

I've encountered a recurring issue with image caching. Specifically, after the cache is cleared, any requests to access images return a 404 error until the cache is eventually repopulated. This issue resolves itself after some time, but it does disrupt the normal flow of operations.

Steps to Reproduce:

GET https://xxxxx.com/v2/etscache/library/nextcloud/manifests/latest: NOT_FOUND: artifact etscache/library/nextcloud:latest not found

Wait about half an hour, get it again, and you can download it

Expected Behavior:
I would expect that there would be a mechanism to either prevent this issue or handle it more gracefully, rather than directly returning a 404 error to the client.

Additional Information:

• Harbor version: 2.7

I understand that this might be due to the cache rebuilding process, but any guidance on how to mitigate this issue or improve the experience would be greatly appreciated.

Thank you for your assistance and the great work you do!

Best regards,
Suning

[wy65701436]

when you refer to cache, are you specifically addressing the cache layer outlined in the harbor yaml? https://github.com/goharbor/harbor/blob/main/make/harbor.yml.tmpl#L300