eiffel-fl

Closing as `traceloop` was totally reworked in inspektor-gadget/inspektor-gadget#1023. I am wondering if we should even archive this repository?

> > Hi! > > Can you use the functions you added in this commit to remove `reflectTypeFromType()` and associated functions? > > Best regards. > > I've used the...

Hi @yuxiang-zhang! Can you please share more context on `--wait=false`? Indeed, we used this flag before but removed it as it is the default behavior: https://github.com/inspektor-gadget/inspektor-gadget/pull/2534#discussion_r1501976294 https://github.com/eksctl-io/eksctl/blob/025550ae2bb64391464314cf762d56781ebf50ed/pkg/ctl/delete/cluster.go#L45 Best regards.

Hi! > Hi @eiffel-fl, we'll need more details on how you configure the cluster and what does your tests do to the VPC/subnets. We also create clusters to run tests...

Hi! I appreciate your reply :smile:! > Hi @eiffel-fl - thanks for explaining your workflow! > > > I would like to avoid using --wait=true, indeed, the cluster creation already...

> I suggest to wait until September :100: :100: :100:! This seems a good idea for me to let two releases and then we delete in the third one. We...

What is the status of this issue? Do we still want to deprecate stuff? If so, we should move forward on this point.

This does not tackle the root cause: ``` command.go:483: Command returned(RunOomkillTestPod): pod/test-pod created command.go:481: Run command(WaitForTestPod): kubectl wait pod --for condition=ready -n test-trace-oomkill-8931607124889025702 test-pod command.go:483: Command returned(WaitForTestPod): error: timed out...

> > Please, see: #2649 > > This is not only about OOMKill. Please see the tests also from the first and last link. The issues we have with the...

> > > I stick to my guns, you can indeed increase the waiting time, but the best solution would be to find the why of this time out. For...