Dashboards are restored automatically with operator.
When the Grafana POD restarts, if a change or a new dashboards has been created without updating operator, IT IS LOST.
With current way of backup/restore Grafana dashboard we face following difficulties :
1) We have 10 minutes to update GitHub configuration before being overwriting by the operator mechanism. We can choose an other period, but we can eliminate the risk to be overwritten. #377
2) We have difficulty to build the right YAML operator for each dashboard (character to be escaped, I experiment loss of information on dashboard after operator run). #608
3) During OPS and IVV activities, we are updating dashboards around 30 times / day.
=> This way of backup / restoring dashboard is not operational for RS operators and engineers.
Environment:
Current Behavior: With v1.5 infrastructure:
With current way of backup/restore Grafana dashboard we face following difficulties : 1) We have 10 minutes to update GitHub configuration before being overwriting by the operator mechanism. We can choose an other period, but we can eliminate the risk to be overwritten. #377
2) We have difficulty to build the right YAML operator for each dashboard (character to be escaped, I experiment loss of information on dashboard after operator run). #608 3) During OPS and IVV activities, we are updating dashboards around 30 times / day.
=> This way of backup / restoring dashboard is not operational for RS operators and engineers.