Kornilios Kourtis

The purpose of this issue is to account for cases where we silently return. It is not about unifying the error maps.

Indeed, this is currently the case, i.e., the policy name should be unique across all other policies. I believe this also includes non-namespaced policies. This can be fixed, but it...

One final request: Can you squash the changes from my feedback into a single commit? (`git rebase --interactive` using the `squash` and `fixup` actions should help).

It's not the intended behavior, and I agree that it's counterintuitive. Originally, Tetragon did not support namespaced policies so we used the policy name as a key, to uniquely identify...

> Would this be something the community would be interested in? I can contribute the change if it's not already being worked on. We 've discussed this in the community...

> @kkourt I created a draft PR here: #2337 > > The namespace policy does get separated: > > ``` > [kind-tetragon-dev|kube-system] (base) ➜ ~ kubectl exec ds/tetragon -c tetragon...

> @kkourt the policies do not seem to be enforced. I also don't see `process_exit` events as you normally should. Any suggestions where to look next? So you mean that...

> @kkourt - Just did a sanity check, I rebuilt the codebase using the `main` branch without these code changes and indeed the sample policies are not taking in effect....

> @kkourt created a separate issue https://github.com/cilium/tetragon/issues/2338 thanks! > Are there any known issues using WSL2? Otherwise, I will have to test in a different environment to confirm this behavior....

> @kkourt @lambdanis - what is the usecase for enabling and disabling a `Sensor`? Since every interaction with Tetragon (as far I can see) goes through a `TracingPolicy`, where is...