You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the metrics and tracing sub-charts are deployed by default on Maesh installation. The purpose of the Helm chart is to install Maesh and to provide the necessary configuration options to be able to use supported metrics and tracing libraries, and not to provide production-ready stacks for metrics and tracing.
Therefore, the metrics and tracing sub-charts must not be deployed by default but should be kept for testing and demonstration purposes.
The text was updated successfully, but these errors were encountered:
I agree with this proposal but it's remains important to provide working and meaningful configurations for metrics and tracing. I suggest to put these files in a contrib folder like on Traefik
For now, I would just keep the Helm chart as is and disable the deployment by default. I also agree that we should find a way to distribute configurations for common tools, like grafana.
Prometheus and Grafana each have an operator to configure them.
You can maybe offer the possibility to deployed grafana dashboard and prometheus job as CRD, in case of the user have installed Prometheus and Grafana with operators.
Feature Request
Proposal
Currently, the metrics and tracing sub-charts are deployed by default on Maesh installation. The purpose of the Helm chart is to install Maesh and to provide the necessary configuration options to be able to use supported metrics and tracing libraries, and not to provide production-ready stacks for metrics and tracing.
Therefore, the metrics and tracing sub-charts must not be deployed by default but should be kept for testing and demonstration purposes.
The text was updated successfully, but these errors were encountered: