Generic tracing example policy not working about tetragon

[mtardy]

Yes exact, you'll need to run the latest build from main, you can do this with:

helm -n kube-system upgrade --install tetragon cilium/tetragon --set tetragon.image.override=quay.io/cilium/tetragon-ci:latest --set tetragonOperator.image.override=quay.io/cilium/tetragon-operator-ci:latest --set imagePullPolicy=Always

Double-check that the installed CRDs in your cluster were upgraded.

Indeed it's not convenient since Tetragon is versioned while our TracingPolicies examples are not, so mismatchs happen :/

[vhgbao01]

Hi, I have already executed the provided command, but unfortunately, I am still encountering the following error:

The TracingPolicy "connect" is invalid: 
spec.kprobes[0].selectors[0].matchArgs[0].operator: Unsupported value: "DAddr": supported values: "Equal", "NotEqual", "Prefix", "Postfix"
spec.kprobes[1].selectors[0].matchArgs[0].operator: Unsupported value: "DAddr": supported values: "Equal", "NotEqual", "Prefix", "Postfix"
spec.kprobes[2].selectors[0].matchArgs[0].operator: Unsupported value: "DAddr": supported values: "Equal", "NotEqual", "Prefix", "Postfix"

I would appreciate any further guidance. Thank you in advance !

[mtardy]

Hi, I have already executed the provided command, but unfortunately, I am still encountering the following error:

The TracingPolicy "connect" is invalid: 

spec.kprobes[0].selectors[0].matchArgs[0].operator: Unsupported value: "DAddr": supported values: "Equal", "NotEqual", "Prefix", "Postfix"

spec.kprobes[1].selectors[0].matchArgs[0].operator: Unsupported value: "DAddr": supported values: "Equal", "NotEqual", "Prefix", "Postfix"

spec.kprobes[2].selectors[0].matchArgs[0].operator: Unsupported value: "DAddr": supported values: "Equal", "NotEqual", "Prefix", "Postfix"

I would appreciate any further guidance. Thank you in advance !

Hey! Let me reopen this issue, clearly we indeed have trouble there as we received multiple reports like that. I'll address this issue this week and get back to you.

[vhgbao01]

Thanks ! It's now working.

[jacobcrawford]

This is not a bug. The examples in the readme were merged to the main branch before the version of Tetragon supporting the "DAddr" operator has been released.
The functionality for "DAddr" is on the main branch as well if you look through the code.

I do agree that this is not convenient for newcomers to the Tetragon repository. 😄

[mtardy]

As we answered this question, I'll close this issue. Please comment again or reopen if you don't agree.

[kevsecurity]

I’ve reverted the changes to the tcp-connect.yaml example so hopefully it will work now.