[resourcedetection] Add api provider to eks detector (#40205)

#### Description
This is a replacement for this PR
#39981

- Expanded the resource attributes to be on par with the EC2 detector
(the new attributes are set to false by default)
#40061
- The EKS detector now uses the newly introduced EKS metadata provider
when the IMDS service is not available
- If IMDS Service is available, we use the EC2 metadata provider

This is needed for EKS clusters that don't have access to IMDS server
and causing the EC2 detector and the accountID/ClusterName attributes in
the EKS detector to fail.

#### Link to tracking issue
Fixes
#39503

<!--Describe what testing was performed and which tests were added.-->
#### Testing
Unit tests coverage
Manual deployment on EKS automode cluster

#### Documentation
In addition to the auto generated doc, I added new content to the
reamdme

Signed-off-by: Dani Louca <[email protected]>

Author: dloucasfx

.chloggen/EKSAutoMode.yaml

@@ -0,0 +1,27 @@
+# Use this changelog template to create an entry for release notes.
+
+# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
+change_type: enhancement
+
+# The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
+component: resourcedetectionprocessor
+
+# A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
+note: Add the option to retrieve resource attributes from the K8s API server and EC2 api when the IMDS service is not available.
+
+# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
+issues: [39503]
+
+# (Optional) One or more lines of additional information to render under the primary note.
+# These lines will be padded with 2 spaces and then inserted directly into the document.
+# Use pipe (|) for multiline entries.
+subtext:
+
+# If your change doesn't affect end users or the exported elements of any package,
+# you should instead start your pull request title with [chore] or use the "Skip Changelog" label.
+# Optional: The change log or logs in which this entry should be included.
+# e.g. '[user]' or '[user, api]'
+# Include 'user' if the change is relevant to end users.
+# Include 'api' if there is a change to a library API.
+# Default: '[user]'
+change_logs: []

processor/resourcedetectionprocessor/README.md

@@ -319,6 +319,12 @@ processors:
 
 ### Amazon EKS
 
+This detector reads resource information from the [EC2 instance metadata service](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html) to retrieve related resource attributes.
+If IMDS is not available, (example: EKS-AutoMode and POD not on the hostnetwork), it falls back to a combination of [Kubernetes API](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.25/#-strong-kubernetes-api-v1-25-strong-) 
+and [EC2 API](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_DescribeInstances.html) to retrieve related resource attributes.
+
+EC2 API requires the `EC2:DescribeInstances` permission to be granted to the IAM role. If IMDS is not accessible, ex: EKS-AutoMode, you can use [POD Identity](https://docs.aws.amazon.com/eks/latest/userguide/pod-identities.html).
+
 The list of the populated resource attributes can be found at [EKS Detector Resource Attributes](./internal/aws/eks/documentation.md).
 
 Example:
@@ -351,6 +357,46 @@ processors:
 Note: The kubernetes cluster name is only available when running on EC2 instances, and requires permission to run the `EC2:DescribeInstances` [action](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_DescribeInstances.html).
 If you see an error with the message `context deadline exceeded`, please increase the timeout setting in your config.
 
+#### Node Name Env Variable
+When using the EC2 API and the Kubernetes API to retrieve resource attributes, the node name is needed. The node name is extracted from the env variable you define on the pod.
+The node name env variable that contains the node name value can be set using the `node_from_env_var` option:
+
+```yaml
+processors:
+  resourcedetection/eks:
+    detectors: [eks]
+    timeout: 15s
+    override: false
+    eks:
+      node_from_env_var: K8S_NODE_NAME
+```
+In this example, the env variable `K8S_NODE_NAME` will hold the actual node name and can be set in the pod spec using the downward API.
+
+```yaml
+        env:
+          - name: K8S_NODE_NAME
+            valueFrom:
+              fieldRef:
+                fieldPath: spec.nodeName
+```
+
+#### IMDS client 
+These options are available to configure the IMDS client:
+
+- `max_attempts`: The maximum number of attempts to make when calling the IMDS endpoint. The default is 3.
+- `max_backoff`: The maximum backoff time to use when retrying a request. The default is 20 seconds.
+
+```yaml
+processors:
+  resourcedetection/eks:
+    detectors: [eks]
+    timeout: 15s
+    override: false
+    eks:
+      max_attempts: 10
+      max_backoff: 5m
+```
+
 ### AWS Lambda
 
 Uses the AWS Lambda [runtime environment variables](https://docs.aws.amazon.com/lambda/latest/dg/configuration-envvars.html#configuration-envvars-runtime)

processor/resourcedetectionprocessor/go.mod

@@ -40,7 +40,6 @@ require (
 	go.uber.org/goleak v1.3.0
 	go.uber.org/multierr v1.11.0
 	go.uber.org/zap v1.27.0
-	k8s.io/client-go v0.32.3
 )
 
 require (
@@ -170,6 +169,7 @@ require (
 	gopkg.in/yaml.v3 v3.0.1 // indirect
 	k8s.io/api v0.32.3 // indirect
 	k8s.io/apimachinery v0.32.3 // indirect
+	k8s.io/client-go v0.32.3 // indirect
 	k8s.io/klog/v2 v2.130.1 // indirect
 	k8s.io/kube-openapi v0.0.0-20241105132330-32ad38e42d3f // indirect
 	k8s.io/utils v0.0.0-20241104100929-3ea5e8cea738 // indirect

processor/resourcedetectionprocessor/internal/aws/eks/config.go

@@ -4,15 +4,24 @@
 package eks // import "github.com/open-telemetry/opentelemetry-collector-contrib/processor/resourcedetectionprocessor/internal/aws/eks"
 
 import (
+	"time"
+
+	"github.com/aws/aws-sdk-go-v2/aws/retry"
+
 	"github.com/open-telemetry/opentelemetry-collector-contrib/processor/resourcedetectionprocessor/internal/aws/eks/internal/metadata"
 )
 
 type Config struct {
 	ResourceAttributes metadata.ResourceAttributesConfig `mapstructure:"resource_attributes"`
+	NodeFromEnvVar     string                            `mapstructure:"node_from_env_var"`
+	MaxAttempts        int                               `mapstructure:"max_attempts"`
+	MaxBackoff         time.Duration                     `mapstructure:"max_backoff"`
 }
 
 func CreateDefaultConfig() Config {
 	return Config{
 		ResourceAttributes: metadata.DefaultResourceAttributesConfig(),
+		MaxBackoff:         retry.DefaultMaxBackoff,
+		MaxAttempts:        retry.DefaultMaxAttempts,
 	}
 }