New EKS cluster may not have aws_auth config map breaking resource detection

[ryanfaircloth]

Component(s)

No response

What happened?

Description

AWS is moving from config_map managed auth to a new feature called access entries, when access entries is enabled the aws_auth is removed this break the current resourcedetection/eks
https://docs.aws.amazon.com/eks/latest/userguide/migrating-access-entries.html

opentelemetry-collector-contrib/processor/resourcedetectionprocessor/internal/aws/eks/detector.go

Line 105 in 609be0a

awsAuth, err := utils.getConfigMap(ctx, authConfigmapNS, authConfigmapName)

Steps to Reproduce

Deploy a collector on a EKS cluster with API only access entries (no aws_auth config map)

Expected Result

EKS should still be the resource type

Actual Result

Collector version

v0.93.0

Environment information

AWS
EKS 1.28
Access Entries enabled aws_auth configmap removed

OpenTelemetry Collector configuration

resourcedetection:
                detectors:
                - env
                - eks

Log output

2024-02-16T16:56:02.022Z        warn    internal/resourcedetection.go:130       failed to detect resource       {"kind": "processor", "name": "resourcedetection", "pipeline": "logs", "error": "isEks() error retrieving auth configmap: failed to retrieve ConfigMap kube-system/aws-auth: configmaps \"aws-auth\" is forbidden: User \"system:serviceaccount:otel-system:otel-collector-cluster\" cannot get resource \"configmaps\" in API group \"\" in the namespace \"kube-system\""}
2024-02-16T16:56:02.023Z        info    internal/resourcedetection.go:139       detected resource information   {"kind": "processor", "name": "resourcedetection", "pipeline": "logs", "resource": {}}

Additional context

No response

[github-actions]

Pinging code owners for processor/resourcedetection: @Aneurysm9 @dashpole. See Adding Labels via Comments if you do not have permissions to add labels yourself.

[crobert-1]

Thanks for posting @ryanfaircloth, I was able to read the links provided and agree this is an issue that needs resolved.

Removing needs triage

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

• processor/resourcedetection: @Aneurysm9 @dashpole

See Adding Labels via Comments if you do not have permissions to add labels yourself.