Private plugin not picked by helm deployment

Grafana Plugin Development Signing & publishing
2

Hi!

  1. Probably because the plugin is either in the wrong path or not signed. I don’t see in your configuration you pointing your plugin folders to an specific place. Are you 100% sure you are putting the sample-plugin archive file in the correct place?
  2. Yes. Except (see the last part of this answer)
  3. The check is local based on the plugin signature and there are some fallbacks for the grafana.com api,. but lack of access to the grafana.com api should not block you from installing a local plugin
  4. You can sign your plugin as a private plugin but you must have access to the grafana.com API to do this. There’s no way to sign a plugin offline. Could you take your plugin files to a system with internet access, sign it and then move the files back to the offline system? You don’t need any further internet connection once is signed.

As a final solution to your problem you can instruct grafana to allow load an specific unsigned plugin via the configuration file. Configure Grafana | Grafana documentation. Do notice having no signature is different from having an invalid signature