Run {agent} on Azure AKS managed by {fleet}

Please follow the steps to run the {agent} on [running-on-kubernetes-managed-by-fleet] page.

Important notes:

On managed Kubernetes solutions like AKS, {agent} has no access to several data sources. Find below the list of the non available data:

Metrics from Kubernetes control plane components are not available. Consequently metrics are not available for kube-scheduler and kube-controller-manager components. In this regard, the respective dashboards will not be populated with data.
Audit logs are available only on Kubernetes master nodes as well, hence cannot be collected by {agent}.
Fields orchestrator.cluster.name and orchestrator.cluster.url are not populated. orchestrator.cluster.name field is used as a cluster selector for default Kubernetes dashboards, shipped with Kubernetes integration.

In this regard, you can use add_fields processor to add orchestrator.cluster.name and orchestrator.cluster.url fields for each Kubernetes integration's component:
Processors configuration
```
- add_fields:
    target: orchestrator.cluster
    fields:
      name: clusterName
      url: clusterURL
```