title: Scaling kube-state-metrics in prometheus-operator
body: <p>In Prometheus-operator, I want to increase the <code>kube-state-metrics</code> replicas to 2. If I increase the replicas, and as the default service discovery role is <code>endpoints</code>, Prometheus will scrape each pod so I'll have all metrics scraped twice that will cause many-to-many issues and it's a waste.</p>
  <p>The issue I had was a node that went down that had the <code>kube-state-metrics</code> on it among others. I didn't know what was going on my cluster till a new pod was scheduled. It's important for me to have the <code>kube-state-metrics</code> redundant.</p>
  <p>How can I configure the <code>kubernetes_sd_configs</code> role for <code>kube-state-metrics</code> to be <code>service</code> so it'll the service as a load balancer and not each pod in the service? OR - how can I scale the <code>kube-state-metrics</code> pods (without sharding)?</p>
  <p>Current config:</p>
  <pre><code>- job_name: monitoring/prometheus-operator-kube-state-metrics/0
    kubernetes_sd_configs:
    - role: endpoints
  </code></pre>
  <p>What I want:</p>
  <pre><code>- job_name: monitoring/prometheus-operator-kube-state-metrics/0
    kubernetes_sd_configs:
    - role: service
  </code></pre>