Kornilios Kourtis
Kornilios Kourtis
In an offline discussion, @mtardy mentioned that: > disable [a policy] without modifying the resource does not sounds very "declarative"/"k8s" way. I think you can end up in a very...
> @kkourt could you please clarify a little bit, does that mean that in order to "disable" policy I will have to delete one and then apply it with some...
> > The idea would be that you will have a field in the policy to disable the policy's functionality and then you would just update the k8s resource (without...
> > (ii) have a DisableTracingPolicy method > > That's what I thought of initially. so I think a DisableTracingPolicy method is perfectly fine for non-k8s use-cases. But for folk...
This has not been updated for a long time. Moving it to draft.
> Hello ! Super glad this is part of the roadmap. > I've been working on this feature few months ago, but it stayed as a WIP and was not...
> ``` > - resolve: "bprm.mm.owner.real_parent.comm" > type: "string" > label: "parent" > ``` > I believe we still need the index to specify which of the function arguments we...
> We can get the argument index from the `btf.FuncParam` type. In the code below, we specify the index to get the BTF type, but we simply need to change...
> I was more expecting to use the parameter name to identify the type because there can only have a single parameter with the same name. Ah I see. A...
> Maybe it could still be helpful to keep the `args:` index and let users choose whether they prefer referring to parameters by name or by position? Yap, I agree...