crane: requesting 1000 tags from quay.io reports that max of 100 tags is exceeded about go-containerregistry HOT 2 CLOSED

We are also hitting this issue. Seems like it's linked to a recent change to Quay which must have just been rolled out to quay.io: quay/quay#2884

There is a small wrinkle though: as per the OCI spec, a client is still allowed to request an arbitrarily high number of tags to be returned in a single API call, which we so far silently ignored and returned the configured maximum. Now we return an HTTP 413 response, which technically is against the spec but needed in order to protect the registry against rogue clients and also return a clear error signal instead of less tags than the client asked for

So their limit always was 100 but was being silently ignored before, whereas now they throw an error.

Seems like there is already logic to set the current 1000 limit for non-Google registries, maybe this now needs a similar check for quay.io to set to n=100?

Or ideally a way to specify the page size via the cli

from go-containerregistry.

It looks like quay fixed this on their end: fluxcd/image-reflector-controller#585 (comment)

from go-containerregistry.