docs: add kernel version-specific selector limits #4553
Merged
Conversation
This file contains hidden or 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
✅ Deploy Preview for tetragon ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
mtardy
reviewed
Jan 22, 2026
| - **Max file match values** (using `fd` or `file` arg): 8 on kernels ≥5.3, 2 on kernels <5.3 | ||
| - **String prefix max length**: 256 chars | ||
| - **String postfix max length**: 128 chars | ||
| - **matchBinaries values**: Unlimited (stored in BPF map) |
Member
There was a problem hiding this comment.
Since there's virtually no limit, you can just remove this
Suggested change
| - **matchBinaries values**: Unlimited (stored in BPF map) |
Comment on lines
2063
to
2065
| - **Max file match values** (using `fd` or `file` arg): 8 on kernels ≥5.3, 2 on kernels <5.3 | ||
| - **String prefix max length**: 256 chars | ||
| - **String postfix max length**: 128 chars |
Member
There was a problem hiding this comment.
Suggested change
| - **Max file match values** (using `fd` or `file` arg): 8 on kernels ≥5.3, 2 on kernels <5.3 | |
| - **String prefix max length**: 256 chars | |
| - **String postfix max length**: 128 chars | |
| - Max file match values (using `fd` or `file` arg): 8 on kernels ≥5.3, 2 on kernels <5.3 | |
| - String prefix max length: 256 chars | |
| - String postfix max length: 128 chars |
Comment on lines
2059
to
2061
| #### Kernel Version-Specific Limits | ||
|
|
||
| Some limits vary based on the kernel version: |
Member
There was a problem hiding this comment.
Tbh I'd just add the things to the list of limitations above without creating a new section, should be good enough and it seems some of your limits don't really depends on kernel versions.
puwun
force-pushed
the
fix/docs-kernel-version-specific-limits
branch
from
cc69e56 to
9f7ba40
Compare
Contributor
Author
|
@mtardy thanks, pushed the changes 👍🏼 |
mtardy
approved these changes
Jan 22, 2026
Member
mtardy
left a comment
mtardy
left a comment
There was a problem hiding this comment.
looks good just one small nit and we can merge
| operators which store values in a BPF map. | ||
|
|
||
|
|
||
|
|
Member
There was a problem hiding this comment.
nit: please remove that whiteline change
Follow-up to PR cilium#4549 documenting additional limits from issue cilium#709. Signed-off-by: Pavan More <[email protected]>
puwun
force-pushed
the
fix/docs-kernel-version-specific-limits
branch
from
9f7ba40 to
af9f118
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Follow-up to #4549 documenting additional limits from #709
Description
Added kernel version-specific limits that were discussed in #709 :
Changelog