Grafana exports Yaml Schema for lower overhead and readability, but GrafanaDashboard objects only support JSON?

[crouth-redge]

Wondering if I've missed something or if there's something undocumented here. Grafana now allows exporting dashboards as YAML, which has much less overhead in terms of bytes (think space limits in etcd) and is far easier to read - however it appears this is overlooked in the operator as it only documents support for JSON and Jsonnet format.

Is yaml support on the roadmap or perhaps already there but poorly documented?

[crouth-redge]

More rough edges here - it seems that GrafanaOperator also doesn't understand v1 schema exports, only "classic" works.

[theSuess]

The new schema is currently still experimental so we haven't added support yet.
Once the API is a bit more mature, we'll look into supporting it.

For the time being you can only use json or jsonnet for inline definitions.
If space is your main concern, you might want to check out https://grafana.github.io/grafonnet which is probably the most concise way to define dashboards right now

[crouth-redge]

v2 Schema is, I think, a separate concern from the v1 Schema, which is stable. However Operator only supports JSON for v1 Schema, when yaml is valid and consumes less data.