<p>I set up datadog trace client in my kubernetes cluster to monitor my deployed application. It was working fine with the kubernetes version 1.15x but as soon as I upgraded the version to 1.16x, the service itself is not showing in the Datadog Dashboard.</p>

<p>Currently using:</p>

<ol>
<li><p>Kubernetes 1.16.9 </p></li>
<li><p>Datadog 0.52.0</p></li>
</ol>

<p>When checked for agent status. It is giving following exception :</p>

<pre><code>Instance ID: kubelet:xxxxxxxxxxxxx [ERROR]
      Configuration Source: file:/etc/datadog-agent/conf.d/kubelet.d/conf.yaml.default
      Total Runs: 12,453
      Metric Samples: Last Run: 0, Total: 0
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 5ms
      Last Execution Date : 2020-06-19 15:18:19.000000 UTC
      Last Successful Execution Date : Never
      Error: Unable to detect the kubelet URL automatically.
      Traceback (most recent call last):
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/base/checks/base.py", line 822, in run
          self.check(instance)
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/kubelet/kubelet.py", line 297, in check
          raise CheckException("Unable to detect the kubelet URL automatically.")
      datadog_checks.base.errors.CheckException: Unable to detect the kubelet URL automatically.
</code></pre>

<p>This looks like a version issue to me. If it is which Datadog version I need to use for monitoring?</p>

<p>This was a issue with deployed DataDog daemonset for me:</p>
<p>What I did to resolve:</p>
<ol>
<li><p>Check daemonset if it exists or not:</p>
<pre><code>kubectl get ds -n datadog
</code></pre>
</li>
<li><p>Edit the datadog daemonset:</p>
<pre><code>kubectl edit ds datadog -n datadog
</code></pre>
</li>
<li><p>In the opened yaml, add</p>
<pre><code>- name: DD_KUBELET_TLS_VERIFY
  value: &quot;false&quot;
</code></pre>
<p>Add this in <strong>env:</strong> tag for all places. For me there were 4 places which are having DD tags in the yaml.</p>
</li>
<li><p>Save and close it. The daemonset will restart. And the application will start getting traced.</p>
</li>
</ol>
