Skip to content

docs: Document BPF_EVENTS requirement#44042

Merged
joestringer merged 1 commit intocilium:mainfrom
EmilyShepherd:docs-bpf-events
Jan 27, 2026
Merged

docs: Document BPF_EVENTS requirement#44042
joestringer merged 1 commit intocilium:mainfrom
EmilyShepherd:docs-bpf-events

Conversation

@EmilyShepherd
Copy link
Copy Markdown
Contributor

When running cilium on kernels that were not compiled with CONFIG_BPF_EVENTS=y, no events are passed from BPF back to userspace, making hubble show no L3/L4 events, without error.

Some discussion of this can be found on #37480.

BPF_EVENTS was enabled and tested in a slim distro here: https://github.com/EmilyShepherd/kiOS/commit/9de663bfcfcf1ad4fa18fb1b15bb75007963bd8d.

Please ensure your pull request adheres to the following guidelines:

  • For first time contributors, read Submitting a pull request
  • All code is covered by unit and/or runtime tests where feasible.
  • All commits contain a well written commit description including a title,
    description and a Fixes: #XXX line if the commit addresses a particular
    GitHub issue.
  • If your commit description contains a Fixes: <commit-id> tag, then
    please add the commit author[s] as reviewer[s] to this issue.
  • All commits are signed off. See the section Developer’s Certificate of Origin
  • Provide a title or release-note blurb suitable for the release notes.
  • Are you a user of Cilium? Please add yourself to the Users doc
  • Thanks for contributing!
docs: Document hubble requirement on kernels with BPF_EVENTS compiled in

When running cilium on kernels that were not compiled with
`CONFIG_BPF_EVENTS=y`, no events are passed from BPF back to
userspace, making hubble show no L3/L4 events, without error.

Resolves cilium#37480

Signed-off-by: Emily Shepherd <emily@redcoat.dev>
@EmilyShepherd EmilyShepherd requested review from a team as code owners January 27, 2026 21:56
@maintainer-s-little-helper maintainer-s-little-helper bot added the dont-merge/needs-release-note-label The author needs to describe the release impact of these changes. label Jan 27, 2026
@EmilyShepherd EmilyShepherd requested a review from qmonnet January 27, 2026 21:56
@github-actions github-actions bot added the kind/community-contribution This was a contribution made by a community member. label Jan 27, 2026
Copy link
Copy Markdown
Member

@joestringer joestringer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks!

@joestringer joestringer added release-note/misc This PR makes changes that have no direct user impact. needs-backport/1.17 This PR / issue needs backporting to the v1.17 branch needs-backport/1.18 This PR / issue needs backporting to the v1.18 branch needs-backport/1.19 This PR / issue needs backporting to the v1.19 branch labels Jan 27, 2026
@maintainer-s-little-helper maintainer-s-little-helper bot removed the dont-merge/needs-release-note-label The author needs to describe the release impact of these changes. label Jan 27, 2026
@joestringer
Copy link
Copy Markdown
Member

/test

@joestringer joestringer enabled auto-merge January 27, 2026 22:06
@joestringer joestringer mentioned this pull request Jan 27, 2026
3 tasks
@joestringer joestringer added this pull request to the merge queue Jan 27, 2026
Merged via the queue into cilium:main with commit 4e7ec78 Jan 27, 2026
83 checks passed
@maintainer-s-little-helper maintainer-s-little-helper bot added the ready-to-merge This PR has passed all tests and received consensus from code owners to merge. label Jan 27, 2026
@mhofstetter mhofstetter mentioned this pull request Jan 29, 2026
6 tasks
@mhofstetter mhofstetter added backport-pending/1.19 The backport for Cilium 1.19.x for this PR is in progress. and removed needs-backport/1.19 This PR / issue needs backporting to the v1.19 branch labels Jan 29, 2026
@mhofstetter mhofstetter mentioned this pull request Jan 29, 2026
6 tasks
@mhofstetter mhofstetter added backport-pending/1.18 The backport for Cilium 1.18.x for this PR is in progress. and removed needs-backport/1.18 This PR / issue needs backporting to the v1.18 branch labels Jan 29, 2026
@mhofstetter mhofstetter mentioned this pull request Jan 29, 2026
2 tasks
@mhofstetter mhofstetter added the backport-pending/1.17 The backport for Cilium 1.17.x for this PR is in progress. label Jan 29, 2026
@mhofstetter mhofstetter removed the needs-backport/1.17 This PR / issue needs backporting to the v1.17 branch label Jan 29, 2026
@github-actions github-actions bot added backport-done/1.17 The backport for Cilium 1.17.x for this PR is done. backport-done/1.19 The backport for Cilium 1.19.x for this PR is done. backport-done/1.18 The backport for Cilium 1.18.x for this PR is done. and removed backport-pending/1.17 The backport for Cilium 1.17.x for this PR is in progress. backport-pending/1.19 The backport for Cilium 1.19.x for this PR is in progress. backport-pending/1.18 The backport for Cilium 1.18.x for this PR is in progress. labels Jan 30, 2026
@cilium-release-bot cilium-release-bot bot moved this to Released in cilium v1.19.0 Feb 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport-done/1.17 The backport for Cilium 1.17.x for this PR is done. backport-done/1.18 The backport for Cilium 1.18.x for this PR is done. backport-done/1.19 The backport for Cilium 1.19.x for this PR is done. kind/community-contribution This was a contribution made by a community member. ready-to-merge This PR has passed all tests and received consensus from code owners to merge. release-note/misc This PR makes changes that have no direct user impact.

Projects

No open projects
Status: Released

Development

Successfully merging this pull request may close these issues.

3 participants