Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BPF] Add support for tracking conntrack metrics in Userspace mode #9741

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

ioworker0
Copy link
Contributor

@ioworker0 ioworker0 commented Jan 22, 2025

Description

When BPFConntrackCleanupMode is set to BPFConntrackModeUserspace, or in cases where the kernel does not support BTF (unfortunately, this is the case with some of our clusters), we are missing metrics related to the conntrack map. These metrics are obviously very useful, so let's also track these metrics under the BPFConntrackModeUserspace setting.

Related issues/PRs

Todos

  • Tests
  • Documentation
  • Release note

Release Note

Add support for tracking conntrack metrics in Userspace mode

Reminder for the reviewer

Make sure that this PR has the correct labels and milestone set.

Every PR needs one docs-* label.

  • docs-pr-required: This change requires a change to the documentation that has not been completed yet.
  • docs-completed: This change has all necessary documentation completed.
  • docs-not-required: This change has no user-facing impact and requires no docs.

Every PR needs one release-note-* label.

  • release-note-required: This PR has user-facing changes. Most PRs should have this label.
  • release-note-not-required: This PR has no user-facing changes.

Other optional labels:

  • cherry-pick-candidate: This PR should be cherry-picked to an earlier release. For bug fixes only.
  • needs-operator-pr: This PR is related to install and requires a corresponding change to the operator.

When BPFConntrackCleanupMode is set to BPFConntrackModeUserspace, or in
cases where the kernel does not support BTF (unfortunately, this is the
case with some of our clusters), we are missing metrics related to the
conntrack map. These metrics are obviously very useful, so let's also track
these metrics under the BPFConntrackModeUserspace setting.

Signed-off-by: Mingzhe Yang <[email protected]>
Signed-off-by: Lance Yang <[email protected]>
@ioworker0 ioworker0 requested a review from a team as a code owner January 22, 2025 11:15
@marvin-tigera marvin-tigera added this to the Calico v3.30.0 milestone Jan 22, 2025
@marvin-tigera marvin-tigera added release-note-required Change has user-facing impact (no matter how small) docs-pr-required Change is not yet documented labels Jan 22, 2025
@ioworker0
Copy link
Contributor Author

CC @tomastigera @fasaxc

@ioworker0
Copy link
Contributor Author

CC @tomastigera @fasaxc

Oops, the commit 'Adding flow log support #9737 ' made similar changes before me. But, I'm just wondering why we use different metrics for BPFConntrackModeUserspace and BPFConntrackModeBPFProgram. Since they both actually do the same task, wouldn't it be better to use the same metric for both as I did? This way would likely be more user-friendly IHMO. wdyt?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs-pr-required Change is not yet documented release-note-required Change has user-facing impact (no matter how small)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants