<p>I got an alert while configuring the monitoring module using <code>prometheus/kube-prometheus-stack 25.1.0</code>.</p>
<p><strong>Alert</strong></p>
<pre><code>[FIRING:1] KubeProxyDown - critical
Alert: Target disappeared from Prometheus target discovery. - critical
 Description: KubeProxy has disappeared from Prometheus target discovery.
 Details:
  • alertname: KubeProxyDown
  • prometheus: monitoring/prometheus-kube-prometheus-prometheus
  • severity: critical
</code></pre>
<p>I think it is a new default rule in <code>kube-prometheus-stack 25.x.x</code>. It does not exist in <code>prometheus/kube-prometheus-stack 21.x.x</code>.</p>
<p>The same issue happened in the EKS and minikube.</p>
<p><strong>KubeProxyDown</strong> Rule</p>
<pre><code>alert: KubeProxyDown
expr: absent(up{job=&quot;kube-proxy&quot;}
  == 1)
for: 15m
labels:
  severity: critical
annotations:
  description: KubeProxy has disappeared from Prometheus target discovery.
  runbook_url: https://runbooks.prometheus-operator.dev/runbooks/kubernetes/kubeproxydown
  summary: Target disappeared from Prometheus target discovery.
</code></pre>
<p>How can I resolve this issue?</p>
<p>I would be thankful if anyone could help me</p>

<p>This is what worked for me in AWS EKS cluster v1.21:</p>
<pre><code>$ kubectl edit cm/kube-proxy-config -n kube-system
---
metricsBindAddress: 127.0.0.1:10249 ### &lt;--- change to 0.0.0.0:10249
$ kubectl delete pod -l k8s-app=kube-proxy -n kube-system
</code></pre>
<p>Note, the name of the config map is <code>kube-proxy-config</code>, not <code>kube-proxy</code></p>
