Kornilios Kourtis

Another thing to note is that the functionality is similar to https://tetragon.io/docs/concepts/tracing-policy/selectors/#follow-children. So I wonder if something like: ``` - matchBinaries: - operator: "In" values: - "/usr/sbin/sshd" followChildren: true -...

One more thing to note is that this looks related to > @kkourt Tetragon currently supports only one match binary operator by selector: https://github.com/cilium/tetragon/blob/main/pkg/selectors/kernel.go#L1426 > > So listing multiple operators...

> @kkourt Hi! I've separated PR into several commits. Thanks! Can you please add some context in the commit messages (see: https://tetragon.io/docs/contribution-guide/submitting-a-pull-request/)? Before merging the PR, we would need tests...

I'm also seeing some CI failures: ``` --- FAIL: TestKprobeSigkillExecveMap1 (306.00s) kprobe_sigkill_test.go:65: child pid is 32313 and spec file is /tmp/sigkill-3506928072.yaml logcapture.go:24: time=2025-10-28T08:17:34.681Z level=INFO msg="BTF discovery: default kernel btf file...

It's not obvious to me that the go test failure is unrelated. The main branch for this test seems to be mostly green https://isovalent.slack.com/archives/C09KTK2PB36/p1761583400602649 and I don't think I've seen...

Hello! > Does Tetragon provide an out-of-the-box solution for this kind of situation? Is using 2 policies the best solution to solve this issue? Today, I think using two policies...

> I can see that if Tetragon reported the status of tracing policies in the CR, the CR user would be able to do something with it, but I wonder...

Thanks! I've raised a [point](https://github.com/cilium/tetragon/issues/4191#issuecomment-3415576691) in the original issue, and I'm not sure if it's addressed here. What happens if the same workload is matched by multiple templates? I'm guessing...

Hi, Thanks! From a first look it makes sense to me. Would it make sense to make things more explicit? For example, have something like: ```yaml spec: globalSelectors: - myapp:...

> What do you think about adding special field then, which will make selector apply to all selectors (maybe something like applyToAll, not sure about this idea actually)? I would...