fix: Using TCP probes for pod liveness and readiness #101
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.
This PR contains a migration on TCP probes from HTTP ones. This migration is required because, due to numerous incoming HTTP requests, the liveness probe cannot successfully return a response. With this fix, the probes will use an endpoint opened using TCP connections, avoiding saturated HTTP pool.
List of Changes
Motivation and Context
These changes are required in order to resolve a problem on saturated HTTP's channels.
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
expected)
Checklist: