I started looking into this. The upgrade itself seems to work fine, however we'll have to ship the https://github.com/grafana/grafana-image-renderer (GIR) if we want to be able to export/share static images. GIR installed via grafana-cli plugins install grafana-image-renderer means having an embedded copy of chromium (leaving aside the fact that we'll have to ship the plugin offline, packaged somehow) which I don't think we really want to do.
Other options as I see them:
- Use GIR releases without chromium (but already built), e.g. at https://github.com/grafana/grafana-image-renderer/releases/download/v2.0.0/plugin-linux-x64-glibc-no-chromium.zip (and packaged)
- Build GIR without chromium ourselves (haven't tried yet) (and packaged)
Soon we'll have Chromium embedded in bootloaders as well...
What is the difference of GIR releases without chromium compared to what grafana-cli would fetch/install? Does it lose some functionablity?
One option for deploying the Grafana plugin(s) (in case more are expected) is a similar approach to the Elastic plugins maybe?
AFAICT there's no difference in the plugin's functionality, GIR has support for using the system's chromium instead of the embedded one (assuming the chromium's version are compatible)
Yes we could ship the plugin offline similarly to what we do with Elastic; we have one more plugin ATM that we ship via scap (operations/software/grafana/simple-json-datasource) although I think switching to Debian packages and ship all plugins would be more convenient
Using the chromium package as packaged in Debian sounds good to me, the only risk is that new versions potentially break the headless setup (but in that case Grafana would also need to update their packages, so seems manageable).