-
Notifications
You must be signed in to change notification settings - Fork 109
Description
I am trying to integrate my EKS cluster using the EKS addon named adot.
I have followed the official AWS documentation of adding the EKS addon in my cluster along the requirements specified in this document.
Note: I have enabled the EKS addon from the AWS console with eks pod identity roles
I am able to a add the EKS addon in my cluster, after which the opentelemetry-operator-system namespace gets created in my cluster along with the following pods in it
After enabling the eks addon i create the ServiceAccount, ClusterRoleBinding, ClusterRole using the following file:
when i deploy the ADOT collector using the following configuration its not scraping any data and also not forwarding any data to new relic(i am using the debug exporter to verify the data):
here is the logs of the adot daemonset collector:
first node daemon collector logs:
adot-deamon-collector-logs1.json
second node daemon collector logs:
adot-deamon-collector-logs2.json
here are logs of the pods running in opentelemetry-operator-system namespace created by enabling the eks addon:
why no data is being scraped by prometheus receiver?