-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
operator: Add support for configuring HTTP server timeouts #9405
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left a few comments in the PR and made a branch with the goal of making the code simpler and avoiding a few indirections. Let me know what you think.
As I mentioned during the daily, I noticed that our defaults for |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Timeout customization seems to work fine in test-cluster. Did not test an actual long-running query yet, though.
[release-5.6] Backport PR grafana#9405
[release-5.7] Backport PR grafana#9405
What this PR does / why we need it:
The server-side timeout (read & write) have been so far constant not-aligned values, i.e. the lokistack-gateway used
12m
and loki1m
. This mismatch yields to server timeouts after one minute when doing long-range queries. This PR adds support to configure these values via the LokiStack custom resource. In addition it aligns the gateway's timeouts with those of Loki by reusing the latter and adding some wiggle room.Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Checklist
CONTRIBUTING.md
guide (required)CHANGELOG.md
updateddocs/sources/upgrading/_index.md