-
-
Notifications
You must be signed in to change notification settings - Fork 589
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
[Traefik] Change transport.respondingTimeouts.readTimeouts to 0 sec #20877
Comments
This comment was marked as spam.
This comment was marked as spam.
Feel free to implement it, instead of making un-allowed and unwanted +1 comments, which may only lead to your comment being hidden, the post being locked and you getting a timeout. |
@Ornias1993 Thanks for your input, I guess yes, I will start by learning docker, kubernets, helms from scratch, and your documentations https://truecharts.org/development/chart-structure/, you can expect my commit ... in about 1-2 months. |
In that case its best to just stfu, basically. Note: In response to above snarky comment. |
Resolved by #22280 |
Is your feature request related to a problem?
https://github.com/traefik/traefik/wiki/respondingTimeouts-for-applications
Basically Traefik introducted respondingTimeouts.readTimeouts of 60 sec as of version 2.11.2, and that may interfere with certain applications, see the tested list in above link
Describe the solution you'd like
Set the value to the old default (0) or if someone wants to really allow it to be changed per ingress I guess it out
Describe alternatives you've considered
Manually editing the deployment to add annotations if there's a chart with an issue on this list https://github.com/traefik/traefik/wiki/respondingTimeouts-for-applications
Additional context
No response
I've read and agree with the following
The text was updated successfully, but these errors were encountered: