<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Kubernetes OneAgent-Deploy Init Container Failure in Container platforms</title>
    <link>https://community.dynatrace.com/t5/Container-platforms/Kubernetes-OneAgent-Deploy-Init-Container-Failure/m-p/237384#M2224</link>
    <description>&lt;P&gt;We found the root cause and solved the issue.&lt;BR /&gt;The issue was that our azure app registration secret that was being used for the dynakube-pull-secret secret in the dynatrace kubernetes namespace had expired.&lt;BR /&gt;This was causing the dynatrace operator to fail pulling from our ACR and for reasons stopped it from updating the&amp;nbsp;&lt;SPAN class=""&gt;dynatrace-dynakube-config secret in our instrumented namespaces from being updated.&amp;nbsp;&lt;BR /&gt;Once we updated secret, injected it into the dynatrace namespace and restarted the operator pod the secret in our instrumented namespaces got updated with new node info.&lt;BR /&gt;Restarting our workloads then resulted in our application being instrumented.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 19 Feb 2024 00:17:40 GMT</pubDate>
    <dc:creator>DynaGibbo</dc:creator>
    <dc:date>2024-02-19T00:17:40Z</dc:date>
    <item>
      <title>Kubernetes OneAgent-Deploy Init Container Failure</title>
      <link>https://community.dynatrace.com/t5/Container-platforms/Kubernetes-OneAgent-Deploy-Init-Container-Failure/m-p/237176#M2219</link>
      <description>&lt;P&gt;We're using cloud native full stack on our linux nodes and pods.&amp;nbsp;&lt;BR /&gt;We use the OneAgent-Deploy init container to instrument our node application.&amp;nbsp;&lt;BR /&gt;Suddenly our newly created nodes are failing to instrument the applications in their pods.&amp;nbsp;&lt;BR /&gt;There is an error in the init container logs saying.&amp;nbsp;&lt;/P&gt;
&lt;P class=""&gt;&lt;SPAN class=""&gt;"level":"info","ts":"2024-02-14T05:07:37.135Z","logger":"standalone-init","msg":"standalone agent init started"}&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class=""&gt;&lt;SPAN class=""&gt;{"level":"info","ts":"2024-02-14T05:07:37.135Z","logger":"standalone-init","msg":"setting host tenant"}&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class=""&gt;&lt;SPAN class=""&gt;{"error":"host tenant info is missing for aks-userreact-80605415-vmss0000x0","level":"error","logger":"standalone-init","msg":"This error has been masked to not fail the container.","stacktrace":"host tenant info is missing for aks-userreact-80605415-vmss0000x0&lt;BR /&gt;&lt;BR /&gt;It seems the secret config value that is printed in the log contains a key value hash of nodes to dynatrace tenant.&amp;nbsp;&lt;BR /&gt;This secret doesn't contain the newly created node name in it.&amp;nbsp;&lt;BR /&gt;eg.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class=""&gt;&lt;SPAN class=""&gt;{"level":"info","ts":"2024-02-14T05:07:37.135Z","logger":"standalone-init","msg":"contents of secret config","content":{...&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class=""&gt;&lt;SPAN class=""&gt;"aks-user-42685077-vmss00004b":"twh49101"...&lt;BR /&gt;&lt;BR /&gt;What is it that populates this key value pair in the config secret?&amp;nbsp;&lt;BR /&gt;What could cause this issue?&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class=""&gt;&lt;SPAN class=""&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 15 Feb 2024 09:20:04 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Container-platforms/Kubernetes-OneAgent-Deploy-Init-Container-Failure/m-p/237176#M2219</guid>
      <dc:creator>DynaGibbo</dc:creator>
      <dc:date>2024-02-15T09:20:04Z</dc:date>
    </item>
    <item>
      <title>Re: Kubernetes OneAgent-Deploy Init Container Failure</title>
      <link>https://community.dynatrace.com/t5/Container-platforms/Kubernetes-OneAgent-Deploy-Init-Container-Failure/m-p/237384#M2224</link>
      <description>&lt;P&gt;We found the root cause and solved the issue.&lt;BR /&gt;The issue was that our azure app registration secret that was being used for the dynakube-pull-secret secret in the dynatrace kubernetes namespace had expired.&lt;BR /&gt;This was causing the dynatrace operator to fail pulling from our ACR and for reasons stopped it from updating the&amp;nbsp;&lt;SPAN class=""&gt;dynatrace-dynakube-config secret in our instrumented namespaces from being updated.&amp;nbsp;&lt;BR /&gt;Once we updated secret, injected it into the dynatrace namespace and restarted the operator pod the secret in our instrumented namespaces got updated with new node info.&lt;BR /&gt;Restarting our workloads then resulted in our application being instrumented.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 19 Feb 2024 00:17:40 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Container-platforms/Kubernetes-OneAgent-Deploy-Init-Container-Failure/m-p/237384#M2224</guid>
      <dc:creator>DynaGibbo</dc:creator>
      <dc:date>2024-02-19T00:17:40Z</dc:date>
    </item>
  </channel>
</rss>

