| Re: [che-dev] Che-operator and Prometheus && Grafana configuration |
_______________________________________________I would recommend a solution that works with both helm and operator. If you the manifests are in the operator image it means that you won't be able to use them with helm. Your command line only tells me that you are creating some configmaps from some json files. But are the json files? Where are you running this command?On Tue, Apr 28, 2020, 07:59 Sergii Kabashniuk <skabashn@xxxxxxxxxx> wrote:You'll have to do deploy dashboards manually.find . -type f -name '*.json' -execdir kubectl create configmap {} --from-file={} \;On Tue, Apr 28, 2020 at 1:39 AM Mario Loriedo <mario.loriedo@xxxxxxxxx> wrote:What I need to do if I want to deploy prometheus + grafana but my deployment method is helm and not the operator?_______________________________________________On Mon, Apr 27, 2020 at 1:28 PM Anatolii Bazko <abazko@xxxxxxxxxx> wrote:Hello.
After some discussion we came to the conclusion that the simplest way is to put json files into a che-operator repository.
There might be some architectural concerns and I would like to hear options.
@David Festal @Nick Boldt @Mario LoriedoOn Thu, Apr 23, 2020 at 2:37 PM Sergii Kabashniuk <skabashn@xxxxxxxxxx> wrote:_______________________________________________On Thu, Apr 23, 2020 at 1:07 PM Anatolii Bazko <abazko@xxxxxxxxxx> wrote:Hello.
I have some concern about putting a json file into the operator container. I am not sure if it is a good approach.
Should we consider something like metadata container and the files in question there?Can you explain more about that to do next with that container?On Thu, Apr 23, 2020 at 12:37 PM Sergii Kabashniuk <skabashn@xxxxxxxxxx> wrote:Hello
I would like to discuss different opportunities
of the way how we can implement the ability of a che-operator to configure Prometheus and Grafana [1].
To be able to do so we need to embed somehow quite a big file that representing Grafana dashboard json
at this moment this is a single YAML/json ~250kb. But in the close future, we are going to split it to multiple (7-9) dashboards ~50k.
I see such ways to do that:
1. Put jsons to https://github.com/eclipse/che-operator and embed jsons directly to executable. Something like https://awesome-go.com/#resource-embedding
2. Put jsons to https://github.com/eclipse/che-operator and later put it to operator image during the docker build phase.After that: configure the operator with the environment variable that points to the folder with jsons.
At this moment I think 2 is better._______________________________________________
[1] https://github.com/eclipse/che/issues/15211 [che-operator] - create ServiceMonitor and GrafanaDashboard when CRDs available and monitoring enabled
[2] https://github.com/eclipse/che/issues/16641 [Monitoring] ConfigMap "che-grafana-dashboards" become too big.--
che-dev mailing list
che-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/che-dev
--_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/che-dev
--
che-dev mailing list
che-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/che-dev
--_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/che-dev
che-dev mailing list
che-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/che-dev
--_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/che-dev
che-dev mailing list
che-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/che-dev