<?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: Azure Kubernete Services (AKS) DIFFERENT of Azure Container Services with Kubernetes (ACS) in Container platforms</title>
    <link>https://community.dynatrace.com/t5/Container-platforms/Azure-Kubernete-Services-AKS-DIFFERENT-of-Azure-Container/m-p/110646#M637</link>
    <description>&lt;P&gt;This is a naming glitch within the documentation between ACS for Kubernetes and AKS.  &lt;/P&gt;&lt;P&gt;For AKS you can install the OneAgent on the compute nodes via the VM-Extension or (even manually) but the preferred way is the kubernetes native operator-rollout mechanism: &lt;A href="https://www.dynatrace.com/support/help/technology-support/cloud-platforms/kubernetes/full-stack/deploy-oneagent-on-kubernetes/"&gt;https://www.dynatrace.com/support/help/technology-...&lt;/A&gt; &lt;/P&gt;&lt;BR /&gt;</description>
    <pubDate>Tue, 26 Feb 2019 08:16:43 GMT</pubDate>
    <dc:creator>patrick_thurner</dc:creator>
    <dc:date>2019-02-26T08:16:43Z</dc:date>
    <item>
      <title>Azure Kubernete Services (AKS) DIFFERENT of Azure Container Services with Kubernetes (ACS)</title>
      <link>https://community.dynatrace.com/t5/Container-platforms/Azure-Kubernete-Services-AKS-DIFFERENT-of-Azure-Container/m-p/110644#M635</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;I'm planning to install OneAgent to monitor Kubernetes on Azure Kubernetes Services (AKS), but in product documentation (&lt;A href="https://www.dynatrace.com/support/help/shortlink/azure-kubernetes" target="_blank"&gt;https://www.dynatrace.com/support/help/shortlink/a...&lt;/A&gt;) I just find procedure to Azure Container Services with Kubernetes (ACS) that is completely different than AKS.&lt;/P&gt;
&lt;P&gt;&lt;IMG src="https://community.dynatrace.com/legacyfs/online/19214-acs-aks.png" border="0" /&gt;&lt;/P&gt;
&lt;P&gt;ACS have a master server that is managed by customer, and in AKS, Microsoft manages the Master server.&lt;/P&gt;
&lt;P&gt;In this documentation, is requested to enable OneAgent extention and 2 data is required:&lt;/P&gt;
&lt;PRE&gt;"&amp;lt;resource group name&amp;gt;" and "&amp;lt;VM name&amp;gt;"&lt;/PRE&gt;
&lt;P&gt;In ACS, I have VMs, but in AKS I just have nodes, not VMs. &lt;STRONG&gt;Question 1:&lt;/STRONG&gt; This command is valid to nodes too?&lt;/P&gt;
&lt;P&gt;If answer for question 1 is yes, we came to &lt;STRONG&gt;Question 2:&lt;/STRONG&gt; I have an auto-scaling enabled, in this scenario, new nodes can be added automatically, how to enable OneAgent extension for all new nodes, auto-scaling can add to my environment?&lt;/P&gt;
&lt;P&gt;According to this blog (&lt;A href="https://www.dynatrace.com/news/blog/managed-kubernetes-azure-check/" target="_blank"&gt;https://www.dynatrace.com/news/blog/managed-kubernetes-azure-check/&lt;/A&gt;) from &lt;A href="https://answers.dynatrace.com/users/28208/view.html" rel="user" target="_blank"&gt;@Katalin Varga&lt;/A&gt;, ACS now is AKS, but both services are quite different, specially to who manage VM Master Server, as I mentioned above.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 10 Dec 2021 08:47:16 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Container-platforms/Azure-Kubernete-Services-AKS-DIFFERENT-of-Azure-Container/m-p/110644#M635</guid>
      <dc:creator>rene_abdon1</dc:creator>
      <dc:date>2021-12-10T08:47:16Z</dc:date>
    </item>
    <item>
      <title>Re: Azure Kubernete Services (AKS) DIFFERENT of Azure Container Services with Kubernetes (ACS)</title>
      <link>https://community.dynatrace.com/t5/Container-platforms/Azure-Kubernete-Services-AKS-DIFFERENT-of-Azure-Container/m-p/110645#M636</link>
      <description>&lt;P&gt;I have the same question, but I am guessing that we should use the "normal" kubernetes deployement to handle the scaling.&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 05 Feb 2019 08:49:50 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Container-platforms/Azure-Kubernete-Services-AKS-DIFFERENT-of-Azure-Container/m-p/110645#M636</guid>
      <dc:creator>anders_lundin3</dc:creator>
      <dc:date>2019-02-05T08:49:50Z</dc:date>
    </item>
    <item>
      <title>Re: Azure Kubernete Services (AKS) DIFFERENT of Azure Container Services with Kubernetes (ACS)</title>
      <link>https://community.dynatrace.com/t5/Container-platforms/Azure-Kubernete-Services-AKS-DIFFERENT-of-Azure-Container/m-p/110646#M637</link>
      <description>&lt;P&gt;This is a naming glitch within the documentation between ACS for Kubernetes and AKS.  &lt;/P&gt;&lt;P&gt;For AKS you can install the OneAgent on the compute nodes via the VM-Extension or (even manually) but the preferred way is the kubernetes native operator-rollout mechanism: &lt;A href="https://www.dynatrace.com/support/help/technology-support/cloud-platforms/kubernetes/full-stack/deploy-oneagent-on-kubernetes/"&gt;https://www.dynatrace.com/support/help/technology-...&lt;/A&gt; &lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 26 Feb 2019 08:16:43 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Container-platforms/Azure-Kubernete-Services-AKS-DIFFERENT-of-Azure-Container/m-p/110646#M637</guid>
      <dc:creator>patrick_thurner</dc:creator>
      <dc:date>2019-02-26T08:16:43Z</dc:date>
    </item>
  </channel>
</rss>

