I'm trying to deploy the kube-prometheus-stack Helm chart in my Kubernetes cluster, but I'm running into some issues. Currently, I have one deployment in the 'monitoring' namespace, and I'm attempting to set up a second instance in the 'pulsar' namespace. However, the Alertmanager pod for the new instance keeps getting stuck in a continuous cycle of Terminating and Pending. I've followed some discussions and suggestions from GitHub (specifically from bitnami) but haven't had any luck. I need to know how to correctly deploy this second instance without causing the Alertmanager to fail in this way. Here are some additional details: I'm using Helm chart version kube-prometheus-stack-72.4.0 with Kubernetes version v1.32.2-gke.1297002. I've made some customizations in values.yaml related to Alertmanager, setting specific namespaces for alertmanagerConfig and prometheusInstance.
3 Answers
Actually, it is possible to run multiple kube-prometheus-stack instances in the same cluster. You just need to install the chart into different namespaces and adjust the default selectors to make sure each instance scrapes different components. Be cautious, though, if you're not experienced with Prometheus, as you can end up with duplicate metrics.
The kube-prometheus-stack wasn't really designed for multiple instances in one cluster. If you just need another Prometheus setup, I suggest using the standard Prometheus Helm chart for the second namespace. It can help avoid the complications from running two kube-prometheus-stacks.
To install the kube-prometheus-stack chart more than once in separate namespaces, you can use Helm commands like this:
`helm install prom1 -n monitoring kube-prometheus-stack`
`helm install prom2 -n pulsar kube-prometheus-stack --set somePort=config`
Just make sure to change any ports that might conflict. Each namespace will have its own service, so this should solve your issues.
Related Questions
How To Get Your Domain Unblocked From Facebook
How To Find A String In a Directory of Files Using Linux