# Azure Kubernete Services (AKS) DIFFERENT of Azure Container Services with Kubernetes (ACS)

**URL:** <https://community.dynatrace.com/t/azure-kubernete-services-aks-different-of-azure-container-services-with-kubernetes-acs/18881>\
**Category:** Container platforms\
**Tags:** azure, kubernetes\
**Created:** [December 18, 2018, 5:50pm UTC](https://community.dynatrace.com/t/azure-kubernete-services-aks-different-of-azure-container-services-with-kubernetes-acs/18881 "2018-12-18T17:50:30Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![rene\_abdon1](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/rene_abdon1/32/28966_2.png) [@rene\_abdon1](https://community.dynatrace.com/u/rene_abdon1)\
**Post date:** [December 18, 2018, 5:50pm UTC](https://community.dynatrace.com/t/azure-kubernete-services-aks-different-of-azure-container-services-with-kubernetes-acs/18881/1 "2018-12-18T17:50:30Z")

</div>

Hi,

I’m planning to install OneAgent to monitor Kubernetes on Azure Kubernetes Services (AKS), but in product documentation ([https://www.dynatrace.com/support/help/shortlink/a…](https://www.dynatrace.com/support/help/shortlink/azure-kubernetes)) I just find procedure to Azure Container Services with Kubernetes (ACS) that is completely different than AKS.

 ![19214-acs-aks.png](https://global.discourse-cdn.com/dynatrace/original/1X/5e79c5554890012d3345dacf4281f086d7dc6d94.png)

ACS have a master server that is managed by customer, and in AKS, Microsoft manages the Master server.

In this documentation, is requested to enable OneAgent extention and 2 data is required:

```auto
"<resource group name>" and "<VM name>"

```

In ACS, I have VMs, but in AKS I just have nodes, not VMs. **Question 1:** This command is valid to nodes too?

If answer for question 1 is yes, we came to **Question 2:** 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?

According to this blog ([Kubernetes monitoring | Kubernetes observability](https://www.dynatrace.com/news/blog/managed-kubernetes-azure-check/)) from [@Katalin Varga](https://answers.dynatrace.com/users/28208/view.html), ACS now is AKS, but both services are quite different, specially to who manage VM Master Server, as I mentioned above.

---

<div class="post-metadata">

**Author:** ![anders\_lundin3](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/anders_lundin3/32/39823_2.png) [@anders\_lundin3](https://community.dynatrace.com/u/anders_lundin3)\
**Post date:** [February 5, 2019, 8:49am UTC](https://community.dynatrace.com/t/azure-kubernete-services-aks-different-of-azure-container-services-with-kubernetes-acs/18881/2 "2019-02-05T08:49:50Z")

</div>

I have the same question, but I am guessing that we should use the “normal” kubernetes deployement to handle the scaling.

---

<div class="post-metadata">

**Author:** ![patrick\_thurner](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/patrick_thurner/32/34782_2.png) [@patrick\_thurner](https://community.dynatrace.com/u/patrick_thurner)\
**Post date:** [February 26, 2019, 8:16am UTC](https://community.dynatrace.com/t/azure-kubernete-services-aks-different-of-azure-container-services-with-kubernetes-acs/18881/3 "2019-02-26T08:16:43Z")

</div>

This is a naming glitch within the documentation between ACS for Kubernetes and AKS.

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: [https://www.dynatrace.com/support/help/technology-…](https://www.dynatrace.com/support/help/technology-support/cloud-platforms/kubernetes/full-stack/deploy-oneagent-on-kubernetes/)
