<p>I'm trying to scrape the AKS kube-proxy metrics with Prometheus without success, the reason is that some of the metrics are only exposed to localhost as the following example:</p>
<pre><code>tcp LISTEN 0  16384  127.0.0.1:10249 *:*                    
</code></pre>
<p>AKS version: 1.16.9</p>
<p>To validate this I also tried to add this to the kube-proxy DeamonSet :</p>
<pre><code>--metrics-bind-address=0.0.0.0
</code></pre>
<p>After the pods restart I can see the metrics, but after some minutes Azure will bring back the version to the managed one, removing the metrics bind address.</p>

Tommy Jimmy Emiliano
<p>There is the following thread: &quot;kube-proxy cannot be scraped for metrics <a href="https://github.com/Azure/AKS/issues/1395" rel="nofollow noreferrer">#1395</a>&quot; at AKS/issues on Github.</p>
<p>As of Sep 2020, the issue is not resolved on AKS 1.16.9, 1.16.10, 1.17.7...</p>
<blockquote>
<p>the metrics are only locally available, it seems it listens to localhost only and can not be accesses from outside. Prometheus can't access it.</p>
</blockquote>
<p>The discussion continued at &quot;Prometheus scrape metrics for kube-proxy <a href="https://github.com/Azure/AKS/issues/1695" rel="nofollow noreferrer">#1695</a>&quot;.
The latest post in that thread is your's, so I assume you are totally aware of how exactly scraping works on AKS as of now :-D (compared to Azure Monitor).</p>
<p>UPD. Just for the sake of &quot;Search engine optimization&quot; (the answer in that github tread) :</p>
<blockquote>
<p>palma21 commented 2 days ago</p>
<p>This was not possible to be changed on the fleet for security concerns on clusters with 1.15 and prior. We'll take a look at this now that 1.15 has been removed.</p>
</blockquote>
