CASMINST-6829 - CSM health checks should detect when Weave has a peer in "sleeve" mode #573
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.
Summary and Scope
If Weave has peers running in "sleeve" mode instead of the fast dataplane (fastdp) mode then pod to pod communication errors can occur resulting in strange behaviour from services running in Kubernetes.
The upgrade procedure has a check for this due to an old issue FN #6636 where the MTU was set incorrectly however the standard CSM health validation tests do not check for this condition.
This PR modifies the
goss-weave-health.yaml
test to check for this condition.Issues and Related PRs
List and characterize relationship to Jira/Github issues and other pull requests. Be sure to list dependencies.
Testing
Tested on:
surtur
Test description:
Verified test works as expected.
Risks and Mitigations
Pull Request Checklist