Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Install Datadog monitoring on EKS using Helm #8

Open
obriensystems opened this issue Dec 18, 2024 · 1 comment
Open

Install Datadog monitoring on EKS using Helm #8

obriensystems opened this issue Dec 18, 2024 · 1 comment
Assignees
@obriensystems

Comments

@obriensystems
Copy link
Member

https://us5.datadoghq.com/signup/agent?platform=kubernetes

helm chart method

helm repo add datadog https://helm.datadoghq.com
helm repo update
kubectl create secret generic datadog-secret --from-literal api-key=9b....8

vi datadog-values.yaml
datadog:
  apiKeyExistingSecret: "datadog-secret"

michaelobrien@mbp8 eks % helm install datadog-agent -f datadog-values.yaml datadog/datadog
NAME: datadog-agent
LAST DEPLOYED: Wed Dec 18 15:31:28 2024
NAMESPACE: default
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
Datadog agents are spinning up on each node in your cluster. After a few
minutes, you should see your agents starting in your event stream:
    https://app.datadoghq.com/event/explorer
You disabled creation of Secret containing API key, therefore it is expected
that you create Secret named 'datadog-secret' which includes a key called 'api-key' containing the API key.

###################################################################################
####   WARNING: Cluster-Agent should be deployed in high availability mode     ####
###################################################################################

The Cluster-Agent should be in high availability mode because the following features
are enabled:
* Admission Controller

To run in high availability mode, our recommendation is to update the chart
configuration with:
* set `clusterAgent.replicas` value to `2` replicas .
* set `clusterAgent.createPodDisruptionBudget` to `true`.

michaelobrien@mbp8 eks % kubectl get pods --all-namespaces -o wide
NAMESPACE      NAME                                           READY   STATUS     RESTARTS   AGE     IP              NODE                            NOMINATED NODE   READINESS GATES
cert-manager   cert-manager-b6fd485d9-cp9pg                   1/1     Running    0          13d     172.31.95.107   ip-172-31-80-165.ec2.internal   <none>           <none>
cert-manager   cert-manager-cainjector-dcc5966bc-jgrxp        1/1     Running    0          13d     172.31.34.155   ip-172-31-42-248.ec2.internal   <none>           <none>
cert-manager   cert-manager-webhook-dfb76c7bd-hwq8d           1/1     Running    0          13d     172.31.32.165   ip-172-31-42-248.ec2.internal   <none>           <none>
default        datadog-agent-cluster-agent-7ff9ffc74d-js69f   1/1     Running    0          33s     172.31.84.250   ip-172-31-80-165.ec2.internal   <none>           <none>
default        datadog-agent-hzb28                            0/3     Init:1/2   0          33s     172.31.93.123   ip-172-31-80-165.ec2.internal   <none>           <none>
default        datadog-agent-sndbf                            2/3     Running    0          33s     172.31.41.181   ip-172-31-42-248.ec2.internal   <none>           <none>
default        helloweb-tls-c66c66fd9-shqdl                   1/1     Running    0          6h34m   172.31.37.227   ip-172-31-42-248.ec2.internal   <none>           <none>
default        reloader-reloader-7bbdd6f96c-xk8xp             1/1     Running    0          7h16m   172.31.95.132   ip-172-31-80-165.ec2.internal   <none>           <none>
kube-system    aws-node-8bwzk                                 2/2     Running    0          55d     172.31.80.165   ip-172-31-80-165.ec2.internal   <none>           <none>
kube-system    aws-node-f9mz4                                 2/2     Running    0          55d     172.31.42.248   ip-172-31-42-248.ec2.internal   <none>           <none>
kube-system    coredns-586b798467-fdvwr                       1/1     Running    0          65d     172.31.80.241   ip-172-31-80-165.ec2.internal   <none>           <none>
kube-system    coredns-586b798467-gff7r                       1/1     Running    0          65d     172.31.88.7     ip-172-31-80-165.ec2.internal   <none>           <none>
kube-system    eks-pod-identity-agent-cq8nn                   1/1     Running    0          55d     172.31.42.248   ip-172-31-42-248.ec2.internal   <none>           <none>
kube-system    eks-pod-identity-agent-g4wxv                   1/1     Running    0          55d     172.31.80.165   ip-172-31-80-165.ec2.internal   <none>           <none>
kube-system    kube-proxy-b8v4z                               1/1     Running    0          55d     172.31.80.165   ip-172-31-80-165.ec2.internal   <none>           <none>
kube-system    kube-proxy-h2ttb                               1/1     Running    0          55d     172.31.42.248   ip-172-31-42-248.ec2.internal   <none>           <none>

forgot
datadog:
  apiKeyExistingSecret: "datadog-secret"
  logs:
    enabled: true
    containerCollectAll: true

bounce the chart

michaelobrien@mbp8 eks % helm repo list                                                   
NAME         	URL                                       
ingress-nginx	https://kubernetes.github.io/ingress-nginx
datadog      	https://helm.datadoghq.com                
michaelobrien@mbp8 eks % helm list             
NAME         	NAMESPACE	REVISION	UPDATED                             	STATUS  	CHART         	APP VERSION
datadog-agent	default  	1       	2024-12-18 15:31:28.384847 -0500 EST	deployed	datadog-3.83.1	7          
michaelobrien@mbp8 eks % helm uninstall datadog-agent
release "datadog-agent" uninstalled


michaelobrien@mbp8 eks % helm install datadog-agent -f datadog-values.yaml datadog/datadog
NAME: datadog-agent
LAST DEPLOYED: Wed Dec 18 15:37:39 2024
NAMESPACE: default
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
Datadog agents are spinning up on each node in your cluster. After a few
minutes, you should see your agents starting in your event stream:
    https://app.datadoghq.com/event/explorer
You disabled creation of Secret containing API key, therefore it is expected
that you create Secret named 'datadog-secret' which includes a key called 'api-key' containing the API key.

###################################################################################
####   WARNING: Cluster-Agent should be deployed in high availability mode     ####
###################################################################################

The Cluster-Agent should be in high availability mode because the following features
are enabled:
* Admission Controller

To run in high availability mode, our recommendation is to update the chart
configuration with:
* set `clusterAgent.replicas` value to `2` replicas .
* set `clusterAgent.createPodDisruptionBudget` to `true`.
*
@obriensystems obriensystems self-assigned this Dec 18, 2024
@obriensystems
Copy link
Member Author

adding
https://docs.datadoghq.com/infrastructure/containers/orchestrator_explorer/?tab=helm

  processAgent:
    enabled: true
  orchestratorExplorer:
    enabled: true


michaelobrien@mbp8 eks % vi datadog-values.yaml                                           
michaelobrien@mbp8 eks % helm list
NAME         	NAMESPACE	REVISION	UPDATED                             	STATUS  	CHART         	APP VERSION
datadog-agent	default  	1       	2024-12-18 15:37:39.791194 -0500 EST	deployed	datadog-3.83.1	7          

michaelobrien@mbp8 eks % helm upgrade datadog-agent -f datadog-values.yaml datadog/datadog
Release "datadog-agent" has been upgraded. Happy Helming!
NAME: datadog-agent
LAST DEPLOYED: Wed Dec 18 16:09:02 2024
NAMESPACE: default
STATUS: deployed
REVISION: 2
TEST SUITE: None
NOTES:
Datadog agents are spinning up on each node in your cluster. After a few
minutes, you should see your agents starting in your event stream:
    https://app.datadoghq.com/event/explorer
You disabled creation of Secret containing API key, therefore it is expected
that you create Secret named 'datadog-secret' which includes a key called 'api-key' containing the API key.

###################################################################################
####   WARNING: Cluster-Agent should be deployed in high availability mode     ####
###################################################################################

The Cluster-Agent should be in high availability mode because the following features
are enabled:
* Admission Controller

To run in high availability mode, our recommendation is to update the chart
configuration with:
* set `clusterAgent.replicas` value to `2` replicas .
* set `clusterAgent.createPodDisruptionBudget` to `true`.
michaelobrien@mbp8 eks % kubectl get pods -n default -o wide      
NAME                                           READY   STATUS    RESTARTS   AGE     IP              NODE                            NOMINATED NODE   READINESS GATES
datadog-agent-cluster-agent-669569858d-4cll7   1/1     Running   0          44s     172.31.41.181   ip-172-31-42-248.ec2.internal   <none>           <none>
datadog-agent-vwzbn                            2/3     Running   0          43s     172.31.34.243   ip-172-31-42-248.ec2.internal   <none>           <none>
datadog-agent-xfffz                            2/3     Running   0          42s     172.31.86.214   ip-172-31-80-165.ec2.internal   <none>           <none>
helloweb-tls-c66c66fd9-shqdl                   1/1     Running   0          7h11m   172.31.37.227   ip-172-31-42-248.ec2.internal   <none>           <none>
reloader-reloader-7bbdd6f96c-xk8xp             1/1     Running   0          7h54m   172.31.95.132   ip-172-31-80-165.ec2.internal   <none>           <none>
michaelobrien@mbp8 eks %

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@obriensystems obriensystems

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@obriensystems