-
Notifications
You must be signed in to change notification settings - Fork 584
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
RFE-3360: add httpRequestTimeout to IngressController CRD #1376
RFE-3360: add httpRequestTimeout to IngressController CRD #1376
Conversation
This helps to better tune slowloris defensive actions.
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: EmmanuelKasper The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Hello @EmmanuelKasper! Some important instructions when contributing to openshift/api: For merging purposes, this repository follows the no-Feature-Freeze process which means that in addition to the standard
OR
Who should apply these qe/docs/px labels?
|
Hi @EmmanuelKasper. Thanks for your PR. I'm waiting for a openshift 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/test-infra repository. |
@EmmanuelKasper https://issues.redhat.com//browse/RFE-3360 is currently on our backlog. In order for the Network Edge team to consider accepting it, we kindly ask you to demonstrate that this change 1) solves the original problem for this customer, and 2) doesn't cause any new performance issues with the router. Benchmark a series of documented performance tests without the change, and then compare it to the same tests with the change. This information will also help you choose the appropriate minimum and maximum values for an openshift/api validation. cc @Miciah |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
@openshift-bot: Closed this PR. In response to this:
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/test-infra repository. |
This helps to better tune slowloris defensive actions.