fix: Set IdleTimeout for http.Server #1418
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
What this PR does / why we need it:
Setup IdleTimeout for ratify http server
Which issue(s) this PR fixes (optional, using
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when the PR gets merged):Fixes #1416
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Yes. I tested this change on an EKS cluster with OPA gatekeeper. Without an idle timeout, gatekeeper audit controller keeps creating new connections till it reaches the OS limit and then any new connection fails. After the change, gatekeeper audit controller still creates new requests, but the connections are short-lived and I no longer encounter the error.
Please describe the tests that you ran to verify your changes. Please also list any relevant details for your test configuration
ss
command on gatekeeper-audit container using ephemeral debug containerChecklist:
Post Merge Requirements
Helm Chart Change