Inspektor Gadget: Expand/improve gadget catalog

[mqasimsarfraz]

Currently, we support a limited number of gadgets providing real-time observability for common Kubernetes use cases. This works well for getting started, but we should also have a generic way to run any supported gadget. Where users can provide more context using their prompts:

For example:

Can you please start a gadget with image ghcr.io/inspektor-gadget/gadget/trace_oomkill in the demo namespace?

While we will continue to expand the list of built-in gadgets based on official gadgets. However, adding a generic way to run gadgets will enable people to use custom observability tools without waiting for them to be added to the default list.

Implementation option:

• Add a gadget_image parameter alongside the existing config here: https://github.com/Azure/aks-mcp/blob/main/internal/components/inspektorgadget/registry.go#L33
• Enforce that only one of gadget_image or gadget_name can be specified
• Start/Run gadget respecting the generic Kubernetes filtering (or allow users to specify custom filtering)

Note: By default, Inspektor Gadget only runs gadgets signed by the Inspektor Gadget team, so only official gadgets will work out of the box. If needed, users can customize their IG installation to allow running additional gadgets.

[sojournerdev]

@mqasimsarfraz

1. Should gadget_image be disabled by default and only enabled via an explicit config flag in aks-mcp? This would give users a safe mode (predefined, signed gadgets only) and an opt-in custom mode (allow custom gadgets with the user taking on additional security responsibility).

2. When custom images are allowed, do we want aks-mcp to enforce its own allowlist/signature/digest checks, or rely entirely on Inspektor Gadget’s defaults?