Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

K8s Spec Mistmatch for uprobes #2323

Closed
joshuajorel opened this issue Apr 11, 2024 · 2 comments
Closed

K8s Spec Mistmatch for uprobes #2323

joshuajorel opened this issue Apr 11, 2024 · 2 comments
Labels
kind/bug Something isn't working

Comments

@joshuajorel
Copy link
Contributor

What happened?

  1. Attempting to do the example for uprobes in the tetragon documentation, I get the following error:
Error from server (BadRequest): error when creating "uprobe.yaml": TracingPolicy in version "v1alpha1" cannot be handled as a TracingPolicy: strict decoding error: unknown field "spec.uprobes[0].symbols"

Checking the CRD, the spec is written as symbol of type string. and not as symbols with a list of strings as type.

Tetragon Version

CLI version: v1.0.1

Kernel Version

Linux ubuntu-noble 6.8.0-11-generic #11-Ubuntu SMP PREEMPT_DYNAMIC Wed Feb 14 00:29:05 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Kubernetes Version

Client Version: v1.29.2
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.28.3

Bugtool

No response

Relevant log output

No response

Anything else?

No response

@joshuajorel joshuajorel added the kind/bug Something isn't working label Apr 11, 2024
@lambdanis
Copy link
Contributor

Hi @joshuajorel thanks for the report. This is a combination of two issues:

So the uprobe example from the docs should work with the main branch of Tetragon (or the next release), but with v1.0.1 you need to change it to have symbol: "readline". This situation is far from ideal, but hopefully it will improve soon.

@mtardy
Copy link
Member

mtardy commented Apr 18, 2024

Thanks Anna for the detailed explanation on this!

I also agree that:

This situation is far from ideal

And sorry for the breakage, but I don't think we can fix something here, next release should naturally "fix" this. Please reopen this issue if you disagree and think some actions could be taken.

@mtardy mtardy closed this as not planned Won't fix, can't repro, duplicate, stale Apr 18, 2024
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants