Windows node agent can't connect to Datadog cluster agent on EKS cluster [BUG]

[julianll1202]

Agent Environment

Output of agent status

 Loading Errors
  ==============
    orchestrator_pod
    ----------------
      Core Check Loader:
        Could not configure check orchestrator_pod: orchestrator check is configured but the cluster name is empty

      Python Check Loader:
        unable to import module 'orchestrator_pod': No module named 'orchestrator_pod'

Describe what happened:
Windows node agent can't connect to Datadog cluster agent on EKS cluster.

Describe what you expected:
Windows node agent connecting to datadog cluster agent and windows pods appearing on datadog's website.

Steps to reproduce the issue:
At the moment I do not know how to reproduce the issue.

Additional environment details (Operating System, Cloud provider, etc):

• Agent version 7.56.0
• Helm chart version 3.70.3
• Kubernetes version 1.29
• Provider AWS
• Cluster type EKS cluster

[mfpierre]

Hi @julianll1202 it seems there could be 2 different issues:

• from the output of the status it seems that the agent is not able to detect automatically the cluster name in your cluster, it's mandatory for the orchestrator check to be able to run, you can set it via the chart or the DD_CLUSTER_NAME env variable
• the issue title is about cluster agent <> node agent communication, do you have more info about that?

[julianll1202]

Yes, I have a mixed cluster (Linux & Windows) and I want my Windows Datadog agent to connect to the Datadog Cluster Agent, which can only be Linux so that I can monitor them