wireguard: Fix traffic counters in cilium debuginfo
#16178
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Wireguard keeps track of the traffic sent and receive for each peer. We print this information in `cilium debuginfo`. Because the agent failed to populate them the JSON response, the counters were always wrongly reported as zero. Signed-off-by: Sebastian Wicki <sebastian@isovalent.com>
gandro
added
release-note/bug
brb
approved these changes
May 17, 2021
|
test-me-please |
|
GH actions seems stuck on the non-required performance tests. Marking this as ready to merge, as all required tests have passed. I have also manually tested this build on EKS. |
gandro
added
the
ready-to-merge
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Wireguard keeps track of the traffic sent and receive for each peer. We
print this information in
cilium debuginfo. Because the agent failedto populate them the JSON response, the counters were always wrongly
reported as zero.