Datadog helm service not running (follow up on prev topic)

[0xbitmonk (Pranav Prakash)]

This is a follow up from prev topic (Possible issue when deploying datadog cluster agent in karpenter).

I followed all the steps mentioned:

1. Added following over ride

# The following YAML contains the minimum configuration required to deploy the Datadog Agent
# on your cluster. Update it accordingly to your needs
datadog:
  # here we use a Qovery secret to retrieve the Datadog API Key (See next step)
  apiKey: qovery.env.DD_API_KEY
  # Update the site depending on where you want to store your data in Datadog
  site: datadoghq.eu
  # Update the cluster name with the name of your choice
  clusterName: fereall
agents:
  tolerations:
    - operator: Exists
  affinity:
    nodeAffinity:
      requiredDuringSchedulingIgnoredDuringExecution:
        nodeSelectorTerms:
          - matchExpressions:
            - key: eks.amazonaws.com/compute-type
              operator: NotIn
              values:
                - fargate

2. Added a priority class. My repo is at GitHub - fere-ai/karpenter-daemonset-priority-class: Simple demo repository to deploy a Helm Chart with a Priority class.

3. Deployed the priority class service. And then re deployed DataDog Service.
4. Still encountering situation where some services are always in “starting” mode. And after 10m (the timeout), the deployment is terminated.

What am I missing?

[ce_gagnaire (Charles-Edouard Gagnaire)]

Hello @0xbitmonk ,

I think you are missing the priority class in your Datadog Configuration.

I’ll get back to you with an example tomorrow.

Regards,
Charles-Edouard

[0xbitmonk (Pranav Prakash)]

Hi @ce_gagnaire , following up on this one.

[ce_gagnaire (Charles-Edouard Gagnaire)]

Yes,

sorry for the delay,

here is an example values.yaml, you will have to adapt based on your configuration.

# The following YAML contains the minimum configuration required to deploy the Datadog Agent
# on your cluster. Update it accordingly to your needs
datadog:
  # here we use a Qovery secret to retrieve the Datadog API Key (See next step)
  apiKey: qovery.env.DD_API_KEY
  # Update the site depending on where you want to store your data in Datadog
  site: datadoghq.eu
  # Update the cluster name with the name of your choice
  clusterName: fereall
clusterAgent:
  priorityClassName:  your_priorityClass
agents:
  # agents.priorityClassName -- Sets PriorityClassName if defined
  priorityClassName:
  tolerations:
    - operator: Exists
  affinity:
    nodeAffinity:
      requiredDuringSchedulingIgnoredDuringExecution:
        nodeSelectorTerms:
          - matchExpressions:
            - key: eks.amazonaws.com/compute-type
              operator: NotIn
              values:
                - fargate

I added

clusterAgent:
  priorityClassName:  your_priorityClass
agents:
  # agents.priorityClassName -- Sets PriorityClassName if defined
  priorityClassName:

I think this may be enough.

Please let me know if you need more assistance on this topic.

Regards,
Charles-Edouard