Qasim Sarfraz
Qasim Sarfraz
This is a great project but as an improvement it should be considered to use a process manager e.g [supercvisor](http://supervisord.org/) along with `crond` to run multiple scripts in reliable way....
Add support for running integration test for local-gadget against multiple container runtimes. Fixes #738
Update the outdated documentation. Related #871 #955
Currently we have scenarios in which if a user runs integration test against a cluster with already deployed SPO we can end up with cleaning everything even if we didn't...
## Current situation Currently nodes with a high number of pods can result in liveness probe check failure e.g #940 resulting in timing out of `kubectl deploy` ## Ideal future...
We know that the workflows triggered via `pull_request` event uses merge commit as `GITHUB_SHA`. Now I would expect that if we change the base branch (using 'edit' button on the...
Currently, we're encountering an issue where attempting to delete a Google Kubernetes Engine (GKE) cluster results in a 400 error if a running job is cancelled during the cluster creation...
## Current situation Currently all the gadgets are published as [packages](https://github.com/orgs/inspektor-gadget/packages?repo_name=inspektor-gadget) in container registry. In order to improve the discovery of the gadgets, we can publish them as a kind...
## Current situation After https://github.com/inspektor-gadget/inspektor-gadget/pull/1532 we are able to support podman (crun) containers. So it makes sense to test `podman` in integration tests as supported runtime. See [comment](https://github.com/inspektor-gadget/inspektor-gadget/pull/1532#issuecomment-1552875445). ## Implementation...