This repository has been archived by the owner on Feb 8, 2024. It is now read-only.
CORTX-33749 - Workaround for conntrack table issues #347
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.
Signed-off-by: Rick Osowski [email protected]
Description
This PR implements a fix for the observed "connection reset by peer" issue resulting in underlying Linux networking configuration issues. It is meant as a reference example for how to manage this issue in a Kubernetes environment.
Type of change
Applicable issues
How was this tested?
Locally and on test machines.
Checklist
If this change requires newer CORTX or third party image versions:
image
fields in solution.example.yaml have been updated to use the required versions.appVersion
field of the Helm chart has been updated to use the new CORTX version.If this change addresses a CORTX Jira issue:
CORTX-XXXXX:
)View rendered README.md
View rendered doc/prereq-deploy-use-cases.md