Marga Manterola
Marga Manterola
Currently, the interaction between the gadget client and the gadget tracer manager is mostly done through CRDs. This is very simple to use for the current setup, but it makes...
## Current situation Currently local-gadget requires a lot of steps in order to run a gadget. This is good for developing and testing, but not particularly user-friendly. ## Impact It's...
Currently, the dns gadget uses the `Stream` output mode. To do this, it uses a gRPC client that runs inside the existing gadget container and communicates with the gRPC server...
Over the past months we've done a lot of work to make our gadgets more consistent. This was tracked in #480. We've made a lot of progress, but there's still...
The idea behind the Network Policy Advisor is very cool but the generated policies are hard to understand. Part of the problem is that the policies are very big and...
Traceloop is not like our other gadgets, it’s “old” (for eBPF purposes), it doesn’t integrate with Gadget Tracer Manager but rather runs as a separate binary. We would like to...
## Description I tried using the seccomp policy advisor to create the policy for a pod in an Azure VM running Ubuntu Hirsute, using Minikube with the driver=none option. I...
## Current situation When creating a trace for the seccomp policy advisor, the user needs to specify the node name, the namespace and the podname that are going to be...
## Current situation Many of our gadgets can filter by typical kubernetes criteria like node, namespace, label, etc. However, it's only possible to select pods or containers that match the...
## Current situation Deploying Inspektor Gadget on the cluster requires running the deploy subcommand and applying the output of that command. There's no HELM chart ## Impact Operators that are...