-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Quay.io: TOO_MANY_TAGS_REQUESTED requested limit 1000 is too high, max is 100 #585
Comments
just tried reaching Quay on X https://x.com/gionn/status/1804162576382664972, it broke all of our Flux automations. |
Major breaking change shipped on a Friday 😱 This also breaks source-controller for HelmCharts and OCIRepositories with semver ranges. |
This is also quay.io images limited, right? Not others. |
yes |
This shouldn't be needed. Quay should return a page with 100 tags (their max page size) along with a link header for the next page. This is how all the other registries behave. |
Is there any way (except recompiling IRC) to get the maximum to 100 in the interim? |
No, the default limit parameter is hard-coded to 1000 and current IRC has no way to change that. |
We (quay.io) have deployed a fix where you'll get the max tags instead of a 417. Sorry for the Friday disruption 😅 |
Thanks @syed Due to exponential backoff in Flux, the ImageRepository reconcilers will take a long time to recover. For a faster recovery, restar image-reflector-controller by deleting its pod. |
Hello, so we have run into an issue that makes us unable to use Image Automation with some Docker Registries which limit PageSize on the
v2/.../.../tags/list
endpoint.In order to resume using Image Automation with Quay.io, we'd need some way of setting
pageSize
on theImageRepository
.The underlying
go-containerregistry.remote
already has awithPageSize
function.https://github.com/google/go-containerregistry/blob/main/pkg/v1/remote/options.go#L292
The text was updated successfully, but these errors were encountered: