What’s Next for the perses-operator

[frezes]

Currently, the Perses Operator project encompasses the implementation of CRDs such as perses, persesdashboard, and persesdatasource, along with functionalities for creating and deleting Perses instances, as well as importing and updating dashboards. However, there are several challenges to address, including the need to trigger instance updates when the perses CR changes and to enhance workload configuration options. Additionally, a significant issue is how to generate corresponding CRs for dashboards created through the UI, effectively using Kubernetes as the database for Perses. What are the plans for future developments in this area?

I am involved in the observability direction at KubeSphere, where we previously had a similar project for custom monitoring that was discontinued for various reasons. I find the Perses project highly intriguing and believe it has great potential for future evolution. Therefore, I plan to implement KubeSphere’s custom monitoring functionality based on the Perses project. At the same time, I would like to contribute to its development and help advance the project.

[jgbernalp]

Thnx for the comment @frezes, all the mentioned topics aer relevant, so I split them into issues for clarity:

• Enhance Perses workload configuration: Enhance Perses workload configuration #23
• Trigger instance updates when Perses CR changes: Trigger instance updates when Perses CR changes #24
• Add option to export Dashboard CR from Perses UI: Add option to export Dashboard CR from Perses UI perses#2417

Please check if they are clear and If you have time we'd appreciate your contribution to these issues.