# Kubernetes how to add scrape\_configs to the running Prometheus?

**URL:** <https://discuss.kubernetes.io/t/kubernetes-how-to-add-scrape-configs-to-the-running-prometheus/19048>\
**Category:** General Discussions\
**Created:** [February 11, 2022, 9:29pm UTC](https://discuss.kubernetes.io/t/kubernetes-how-to-add-scrape-configs-to-the-running-prometheus/19048 "2022-02-11T21:29:25Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![lk7777](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/lk7777/32/9508_2.png) [@lk7777](https://discuss.kubernetes.io/u/lk7777)\
**Post date:** [February 11, 2022, 9:29pm UTC](https://discuss.kubernetes.io/t/kubernetes-how-to-add-scrape-configs-to-the-running-prometheus/19048/1 "2022-02-11T21:29:25Z")

</div>

Hi All,

### Cluster information:

Kubernetes version: k3s v1.23.2  
Cloud being used: bare-metal  
Installation method: helm  
Host OS: Proxmox (VMs: Ubuntu 20.04)

k3s 1 master, 2 workers

I am new to Kubernetes and Prometheus.

Prometheus installed by using the helm [chart](https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stack)

How can I add/patch an additional scrape\_configs to the running Prometheus?

```auto
scrape_configs:
- job_name: master-node
  scrape_interval: 15s
  static_configs:
  - targets: ['10.10.5.70:9100']
  metrics_path: /metrics

```

It uses prometheus-prometheus-kube-prometheus-prometheus (secret) for configuration.

---

<div class="post-metadata">

**Author:** ![lk7777](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/lk7777/32/9508_2.png) [@lk7777](https://discuss.kubernetes.io/u/lk7777)\
**Post date:** [February 24, 2022, 3:57pm UTC](https://discuss.kubernetes.io/t/kubernetes-how-to-add-scrape-configs-to-the-running-prometheus/19048/2 "2022-02-24T15:57:31Z")

</div>

Couldn’t find any way to add targets outside of the k3s cluster to the helm Prometheus. It seems that the helm installation is only for the targets in the kubernetes cluster environment, so it doesn’t fit my needs.  
I ended up installing Prometheus with yaml(s) w/o the operator. Learned a lot comparing to the helm installation. Now I have a freedom of installing only necessary components which I understand and any target that I wish by adding them to the ConfigMap. For my small environment I do not need that enormous helm Prometheus deployment with myriads of questionable scrape jobs/alerts and metrics. This is when I started to understand Grafana/Prometheus dashboards.

---

<div class="post-metadata">

**Author:** ![parandhama\_reddy](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/parandhama_reddy/32/11502_2.png) [@parandhama\_reddy](https://discuss.kubernetes.io/u/parandhama_reddy)\
**Post date:** [March 30, 2023, 3:39pm UTC](https://discuss.kubernetes.io/t/kubernetes-how-to-add-scrape-configs-to-the-running-prometheus/19048/3 "2023-03-30T15:39:36Z")

</div>

can you please share the solution how to add those scrape config…even i need to add this config in kubernetes @lk7777