tetragon
tetragon copied to clipboard
Document the available types of arguments for `kprobes` and `tracepoints`
The documentation is now pointing to the CRD for the definition of the list of possible arguments but we could improve that to detail:
- What is the argument type
- How can it be compared. How operators are working on the types.
For example, the file type is the kernel file structure but can be compared with string directly, comparing the path.
/assign
Where should that documentation go? Could you perhaps seed a complete initial entry e.g. for file so we can target a common style?