-
Notifications
You must be signed in to change notification settings - Fork 83
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-app(Route-timeout): increasing timeout for external S3 Storage system with larger images (PROJQUAY-7670) #942
base: master
Are you sure you want to change the base?
Conversation
Hi @michaelalang. Thanks for your PR. I'm waiting for a quay member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
0aee4d9
to
f9aab74
Compare
/ok-to-test |
f9aab74
to
4f56f33
Compare
- Fix kustomize path for clairpgupgrade when clair is managed/unmanaged
- Remove base from pgupgrade path to ensure that the file location is parsed properly by kustomize package
Bumps [github.com/jackc/pgx/v4](https://github.com/jackc/pgx) from 4.11.0 to 4.18.2. - [Changelog](https://github.com/jackc/pgx/blob/v4.18.2/CHANGELOG.md) - [Commits](jackc/pgx@v4.11.0...v4.18.2) --- updated-dependencies: - dependency-name: github.com/jackc/pgx/v4 dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]>
@ibazulic wait ... there's some commit's in this PR that shouldn't be in ... trying to fix |
4f56f33
to
f48a30a
Compare
With various new Storage Class integrations and possible delays in moving the multi-part objects to it's final destination, we've seen various timeouts being raised even though multi-parts have been uploaded successful.
These timeout's are not happening during uploads but when the client(s) wait for Quay to complete the multi-parts which might take more than the currently defined
10m
It's further to notice that sharding should be considered to avoid affecting other Ingress connections which do not have such a long duration.