Component(s)

processor/resourcedetection

What happened?

Description

We've recently lost EKS resource attributes on our telemetry data following an upgrade of an EKS cluster to K8s version 1.35 (EKS platform version eks.3). This resulted from a change in the server version (git version) format for new EKS builds; the server version returned from the K8s version API no longer includes the substring identifier -eks-.

Steps to Reproduce

Run an OpenTelemetry collector workload with EKS resource detection configured on an up to date EKS cluster (K8s version >=1.35). Verify that the server version format does not include the substring identifier -eks-:

$ kubectl version
Client Version: v1.31.1
Kustomize Version: v5.4.2
Server Version: v1.35.0-33+37970203ae1a44

Expected Result

The resource detection processor detects it's running as an EKS workload and enriches telemetry data with EKS resource attributes.

Actual Result

The resource detection processor does not enrich telemetry data with EKS resource attributes.

Collector version

v0.144.0

Environment information

Environment

EKS: K8s version 1.35, platform version eks.3
OS: Bottlerocket 1.54.0

OpenTelemetry Collector configuration

receivers:
  otlp:
    protocols:
      grpc:
        endpoint: 0.0.0.0:4317

processors:
  resourcedetection:
    detectors:
    - eks
    eks:
      node_from_env_var: K8S_NODE_NAME
      resource_attributes:
        k8s.cluster.name:
          enabled: true

exporters:
  debug:
    verbosity: detailed

service:
  pipelines:
    traces:
      receivers:
      - otlp
      processors:
      - resourcedetection
      exporters:
      - debug

Log output

No response

Additional context

No response

Tip

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.}