# Configuring cluster name in the AKS extension

**URL:** <https://community.dynatrace.com/t/configuring-cluster-name-in-the-aks-extension/56504>\
**Category:** Container platforms\
**Tags:** dynatrace-operator, kubernetes\
**Created:** [July 20, 2026, 1:52pm UTC](https://community.dynatrace.com/t/configuring-cluster-name-in-the-aks-extension/56504 "2026-07-20T13:52:08Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![glenthomas](https://avatars.discourse-cdn.com/v4/letter/g/4491bb/32.png) [@glenthomas](https://community.dynatrace.com/u/glenthomas)\
**Post date:** [July 20, 2026, 1:52pm UTC](https://community.dynatrace.com/t/configuring-cluster-name-in-the-aks-extension/56504/1 "2026-07-20T13:52:08Z")

</div>

I am using the Dynatrace AKS extension and there appears to be no way to configure the cluster name, so the data all comes through with cluster name “dynatrace”, which is not very useful.

There is no documented way to configure the cluster name and support told me to not use the AKS extension.

So, is there some way to configure the cluster name that I don’t know about, or could this be added into the extension configuration settings?

---

<div class="post-metadata">

**Author:** ![marina\_pollehn](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/marina_pollehn/32/39120_2.png) [@marina\_pollehn](https://community.dynatrace.com/u/marina_pollehn)\
**Post date:** [July 21, 2026, 9:52am UTC](https://community.dynatrace.com/t/configuring-cluster-name-in-the-aks-extension/56504/2 "2026-07-21T09:52:47Z")

</div>

![marina_pollehn_1-1784626434816.png](https://global.discourse-cdn.com/dynatrace/original/2X/6/6008494429a048090b35885d924202733662f8df.png)

When I configure the extension I do have control over the naming of the cluster, see screenshot below.

 ![marina_pollehn_0-1784626354505.png](https://global.discourse-cdn.com/dynatrace/original/3X/2/9/293f2de95cdb8f27379d72352a9139f7e9a3a183.png)

If I already did the deployment, I change the cluster name via the new Kubernetes app. I select the cluster and go to Settings via the three dots

![marina_pollehn_3-1784627502324.png](https://global.discourse-cdn.com/dynatrace/optimized/3X/b/c/bc79d918733833890b61426af4bbb9769d0bd6ca_2_690x46.png)

and then head to Collect & Capture \>\> Kubernetes cluster connection

 ![marina_pollehn_2-1784626757190.png](https://global.discourse-cdn.com/dynatrace/original/2X/6/657f419bd010d98a721c94fa66f1fa28731748c9.png)

Is this working for you?

---

<div class="post-metadata">

**Author:** ![marina\_pollehn](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/marina_pollehn/32/39120_2.png) [@marina\_pollehn](https://community.dynatrace.com/u/marina_pollehn)\
**Post date:** [July 21, 2026, 9:53am UTC](https://community.dynatrace.com/t/configuring-cluster-name-in-the-aks-extension/56504/3 "2026-07-21T09:53:48Z")

</div>

We are talking about the same extension, right?

---

<div class="post-metadata">

**Author:** ![glenthomas](https://avatars.discourse-cdn.com/v4/letter/g/4491bb/32.png) [@glenthomas](https://community.dynatrace.com/u/glenthomas)\
**Post date:** [July 21, 2026, 10:57am UTC](https://community.dynatrace.com/t/configuring-cluster-name-in-the-aks-extension/56504/4 "2026-07-21T10:57:38Z")

</div>

Your screenshots are from the Dynatrace UI, which generates Helm/manifest files for deploying the Dynatrace Kubernetes integration to a cluster.

I am using the Dynatrace AKS Marketplace extension, which I am deploying via Terraform. I guess there may be a configuration setting that allows setting the cluster name, but I don’t know what it is.

 ![glenthomas_0-1784631288787.png](https://global.discourse-cdn.com/dynatrace/original/3X/4/b/4be269aacb4fe96c7917e08c86787f48280b21d4.png)

```markup
resource "azurerm_kubernetes_cluster_extension" "dynatrace" {
  name = module.managed_cluster.name
  cluster_id = module.managed_cluster.resource_id
  extension_type = "dynatrace.azuredynatraceoperator.one.x"

  plan {
    name = "dynatrace-operator-1-x"
    product = "azure-dynatrace-operator"
    publisher = "dynatrace"
  }

  configuration_settings = {
    "dynatrace-operator-azure.apiurl" = var.dynatrace_api_url
    "dynatrace-operator-azure.mode" = "cloudNativeFullStack"
  }

  configuration_protected_settings = {
    "dynatrace-operator-azure.apitoken" = var.dynatrace_api_token
    "dynatrace-operator-azure.dataingesttoken" = var.dynatrace_data_ingest_token
  }

  depends_on = [azurerm_marketplace_agreement.dynatrace]
}

resource "azurerm_marketplace_agreement" "dynatrace" {
  publisher = "dynatrace"
  offer = "azure-dynatrace-operator"
  plan = "dynatrace-operator-1-x"
}

```

---

<div class="post-metadata">

**Author:** ![glenthomas](https://avatars.discourse-cdn.com/v4/letter/g/4491bb/32.png) [@glenthomas](https://community.dynatrace.com/u/glenthomas)\
**Post date:** [July 21, 2026, 12:32pm UTC](https://community.dynatrace.com/t/configuring-cluster-name-in-the-aks-extension/56504/5 "2026-07-21T12:32:44Z")

</div>

My understanding is that the Dynatrace operator takes the cluster name from the name of the DynaKube resource.

I described the dynakube resource (`kubectl get dynakube -n dynatrace`) and the name is the cluster name.

```markup
Name: my-cluster
Namespace: dynatrace
Kind: DynaKube

```

Maybe the cluster name was set in Dynatrace by my initial configuration, which has since changed, and it is not updating. I don’t see any way in Dynatrace to remove and re-register the cluster.

---

<div class="post-metadata">

**Author:** ![glenthomas](https://avatars.discourse-cdn.com/v4/letter/g/4491bb/32.png) [@glenthomas](https://community.dynatrace.com/u/glenthomas)\
**Post date:** [July 21, 2026, 1:58pm UTC](https://community.dynatrace.com/t/configuring-cluster-name-in-the-aks-extension/56504/6 "2026-07-21T13:58:49Z")

</div>

I have managed to get it working. I think the fix was to change the AKS extension name to the name of the cluster. Previously we named it “dynatrace”, because I didn’t understand that the extension name was used to populate the cluster name field.

Then I had to go into the Connection settings in the Dynatrace UI and delete the cluster connection settings for the clusters. Then they reappeared with the correct cluster names.

Problem solved.
