In order to enable direct access to the API server, we need a way for the front-end grafana plugin to communicate directly with the API server using grafana auth. The likely most feasible way to do this (at least initially) is to have the k3d API extensions server (which serves CRD's) aggregated under the grafana API server, so that a front-end plugin can talk to the grafana API server to access their CRDs.
We need a solution that works with the manifests generated by grafana-app-sdk project local generate that will enable a front-end plugin to take the same actions on their kinds as the back-end plugin currently can, without needing that back-end proxy.
toddtreece
commented
2 months ago
In order to enable direct access to the API server, we need a way for the front-end grafana plugin to communicate directly with the API server using grafana auth. The likely most feasible way to do this (at least initially) is to have the k3d API extensions server (which serves CRD's) aggregated under the grafana API server, so that a front-end plugin can talk to the grafana API server to access their CRDs.
We need a solution that works with the manifests generated by
grafana-app-sdk project local generatethat will enable a front-end plugin to take the same actions on their kinds as the back-end plugin currently can, without needing that back-end proxy.