Update OSS Collector setup page for GKE, AKS, and EKS Auto Mode

[brett0000FF]

What does this PR do? What is the motivation?

Syncs Set Up the OpenTelemetry Collector (OSS) with the latest recommended OTLP-only Collector configurations in opentelemetry-examples, which added GKE, AKS, and EKS Auto Mode support.

New environment support (the ask):

• Prerequisites now list Amazon EKS (including Auto Mode), Google GKE (Standard and Autopilot), and Azure AKS (including Automatic).
• New Managed Kubernetes distributions section in the Kubernetes (DaemonSet) tab with the resource_detection processor for each environment, the IMDS token hop limit requirement (EKS), the Pod Identity and EC2:DescribeInstances requirement (EKS Auto Mode), and the host port and /hostfs restrictions on GKE Autopilot and AKS Automatic.
• Helm chart tab lists the per-environment values files.

Sync work that comes with it:

• Collector Contrib v0.154.0, which is where the snake_case component names used by the recommended configs apply (host_metrics, resource_detection, span_metrics, forward/traces_sample). The new per-environment snippets are drop-in replacements for the base config, so the base config had to use the same names.
• sending_queue.batch now flushes at 2 MiB and splits at 4 MiB, matching the upstream change that keeps requests under the intake payload limit.
• The Kubernetes config gains the kubelet_stats receiver and deltatorate processor. These were already upstream but missing here, and they are what supplies node, pod, and container metrics on GKE Autopilot and AKS Automatic, where host_metrics cannot run.
• The DaemonSet tab documents the environment variables and the ClusterRole rules the config depends on, including nodes/stats for kubelet_stats.
• Docker tab documents OTEL_RESOURCE_ATTRIBUTES and bumps the image tag.

Merge instructions

Merge readiness:

• Ready for merge

Additional notes

Two things worth a look from the OTel team:

1. daemonset-eks-auto.yaml configures an ec2: detector block, but ec2 is not in its detectors list, so the kubernetes.io/cluster/* tag collection it sets up does not run. It looks like a copy-paste from daemonset-eks.yaml. It is omitted from the docs snippet.
2. agent.yaml sets deployment_type: daemonset for an uncontainerized host install. The docs mirror it as-is, but it may be worth correcting upstream.

Also: the experimental-oss-config branch is referenced by 10 links on this page. If that branch merges to main, the links need updating.

🤖 Generated with Claude Code

[github-actions]

Preview links (active after the build_preview check completes)

Modified Files

• https://docs-staging.datadoghq.com/brett.blue/otlp-oss-config-update/opentelemetry/setup/collector_exporter/oss_setup