Defender daemonset deployment in Alibaba Kubernetes Cluster

Cluster name does not get resolved to the actual name of the cluster in Prisma when deploying the defender daemonset in Alibaba Kubernetes Cluster

**Product_versions**
• Product: Prisma Cloud Compute

**Topology/Configuration**
Alibaba Kubernetes Cluster (ACK)

This is how the cluster name resolution algorithm works on the defender side:

1. A general cluster discovery routine looks for well-known kubelet configuration files like /etc/kubernetes/kubelet.conf, /var/lib/kubelet/kubelet.conf, /etc/eksctl/kubeconfig.yaml and others. If one of them is found, we look for the "server" section within the file and we strip any "https" prefix and ports from it. 
2. After that, A cloud-specific resolver overrides the previous stage. We currently don't have cloud resolvers for ACK. So in this stage we don't override the previous result like we do for other clouds like AWS, GCP, Azure.
3. This may lead to inconsistent cluster name being shown in Prisma for e.g "apiserver" instead of the actual cluster name in ACK

To avoid inconsistent cluster names in ACK, we need to set the cluster name manually as follows:

1. Navigate to Manage > Defenders > Manual Deploy > Advanced Settings.
2. Change 'Cluster name resolving method' to 'Manual' from the dropdown.
3. Enter your cluster name in the 'Specify a cluster name' field.