> ## Documentation Index
> Fetch the complete documentation index at: https://docs.raven.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Kubernetes Cluster Name

> Setting Kubernetes Cluster Name instructions

## Kubernetes Cluster Name Automatic Detection

The Raven Sensor can automatically detect the Kubernetes cluster name. If detected, the cluster name is added as a label to all data collected. This facilitates the identification of nodes and its related data across Kubernetes clusters.

On Azure AKS, Kubernetes Cluster Name Automatic Detection is currently not supported. Please specify the cluster name manually via the sensor.spec.clusterName section in the values.yaml

On GCP GKE, the cluster name is retrieved from the cloud provider API.

On Amazon EKS, the cluster name is retrieved from EC2 instance tags. For the Raven Agent to query EC2 instance tags, you must add the `ec2:DescribeInstances` permission to your Raven Agent IAM policy using [IAM Roles for Service Accounts (IRSA)](https://docs.aws.amazon.com/emr/latest/EMR-on-EKS-DevelopmentGuide/setting-up-enable-IAM.html).

Assuming you have created an IAM role with the required policies attached and it is called `arn:aws:iam::XXXXXXXXXXXX:role/raven-sensor`. You can use the following parameters while installing the agent using the official helm chart to attach the role to the relevant service account:

```yaml theme={null}
sensor:
  serviceAccount:
    annotations:
      eks.amazonaws.com/role-arn: arn:aws:iam::XXXXXXXXXXXX:role/raven-sensor
```

<Warning>
  The application does not require the use of AWS account root privileges for deployment or operation.
</Warning>

## Manually setting cluster name

Note: You can manually set this cluster name value by using Agent configuration parameter `sensor.spec.clusterName` or the `CLUSTER_NAME` environment variable.