<?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: OneAgent Installation on Kubernetes using Daemonset versus Operator in Container platforms</title>
    <link>https://community.dynatrace.com/t5/Container-platforms/OneAgent-Installation-on-Kubernetes-using-Daemonset-versus/m-p/125857#M571</link>
    <description>&lt;P&gt;Hi Ma,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;OneAgent installation with the operator is preferred as it will allow the agent to be automatically updated. The Operator still uses the daemonset but it is handled for you once the operator is installed. Unfortunately the operator only works with Kubernetes version 1.9+, so for versions 1.8 or lower you will still need to manually deploy the Daemonset.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;You can read more about the OneAgent Operator here: &lt;A href="https://www.dynatrace.com/support/help/technology-support/cloud-platforms/openshift/installation-and-operation/full-stack/what-is-oneagent-operator/"&gt;https://www.dynatrace.com/support/help/technology-support/cloud-platforms/openshift/installation-and-operation/full-stack/what-is-oneagent-operator/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Jonny&lt;/P&gt;&lt;BR /&gt;</description>
    <pubDate>Tue, 10 Dec 2019 17:15:37 GMT</pubDate>
    <dc:creator>jonathan_schull</dc:creator>
    <dc:date>2019-12-10T17:15:37Z</dc:date>
    <item>
      <title>OneAgent Installation on Kubernetes using Daemonset versus Operator</title>
      <link>https://community.dynatrace.com/t5/Container-platforms/OneAgent-Installation-on-Kubernetes-using-Daemonset-versus/m-p/125856#M570</link>
      <description>&lt;P&gt;Hi all, Can someone explain me why installation of OneAgent with Kubernetes version 1,9 uses Operator while lower version uses daemonset?Thank you.&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 10 Dec 2019 03:24:03 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Container-platforms/OneAgent-Installation-on-Kubernetes-using-Daemonset-versus/m-p/125856#M570</guid>
      <dc:creator>aurora</dc:creator>
      <dc:date>2019-12-10T03:24:03Z</dc:date>
    </item>
    <item>
      <title>Re: OneAgent Installation on Kubernetes using Daemonset versus Operator</title>
      <link>https://community.dynatrace.com/t5/Container-platforms/OneAgent-Installation-on-Kubernetes-using-Daemonset-versus/m-p/125857#M571</link>
      <description>&lt;P&gt;Hi Ma,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;OneAgent installation with the operator is preferred as it will allow the agent to be automatically updated. The Operator still uses the daemonset but it is handled for you once the operator is installed. Unfortunately the operator only works with Kubernetes version 1.9+, so for versions 1.8 or lower you will still need to manually deploy the Daemonset.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;You can read more about the OneAgent Operator here: &lt;A href="https://www.dynatrace.com/support/help/technology-support/cloud-platforms/openshift/installation-and-operation/full-stack/what-is-oneagent-operator/"&gt;https://www.dynatrace.com/support/help/technology-support/cloud-platforms/openshift/installation-and-operation/full-stack/what-is-oneagent-operator/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Jonny&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 10 Dec 2019 17:15:37 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Container-platforms/OneAgent-Installation-on-Kubernetes-using-Daemonset-versus/m-p/125857#M571</guid>
      <dc:creator>jonathan_schull</dc:creator>
      <dc:date>2019-12-10T17:15:37Z</dc:date>
    </item>
  </channel>
</rss>

