search

carlosedp / cluster-monitoring

Cluster monitoring stack for clusters based on Prometheus Operator
MIT License
740 stars 201 forks source link

Two (not related) Prometheus instances #113

Closed jamessewell closed 3 years ago

jamessewell commented 3 years ago

Love this repo!

I am trying to work out how I deploy two Proms in one namespace (one will be for k8s, and the other will be for app data - with different retentions).

I thought this would work:

 prometheus+:: {
    // Add option (from vars.yaml) to enable persistence
    local pvc = k.core.v1.persistentVolumeClaim,
    apps+: {
      spec+: {
...
...
   prometheus+: {
      spec+: {

But I only get the storage stuff in ./manifests/prometheus-apps.yaml, not the rest.

Any ideas?

I'm hoping to have a service and grafana datasource for each.

carlosedp commented 3 years ago

Thanks! This monitoring stack was not planned to have multiple Prometheus instances on the same namespace. I suggest having them separately.

jamessewell commented 3 years ago

The issue is that you can’t really run multiple Prometheus operators in a cluster - so another instance kinda has to be integrated.

On Wed, 26 May 2021 at 11:32 pm, Carlos Eduardo @.***> wrote:

Closed #113 https://github.com/carlosedp/cluster-monitoring/issues/113.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/carlosedp/cluster-monitoring/issues/113#event-4799415459, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJJDIZQRLQLCUD7JTQBQ3LTPT2ALANCNFSM45RIA3YQ .