[EDOT Collector] Depecation warnings

[ltflb-bgdi]

Today I updated our operators to v9.4.3 to have deprecation warnings fixed.
Now the logs report two new deprecation warnings, both coming from your values.yaml:

{"level":"warn","ts":"2026-07-03T13:27:18.592Z","caller":"builders/builders.go:40","msg":"\"hostmetrics\" alias is deprecated; use \"host_metrics\" instead","resource":{"k8s.pod.name":"opentelemetry-kube-stack-daemon-collector-9rvr4","service.instance.id":"950b952c-3df6-46ed-aa60-e4c1ea57ce59","service.name":"elastic-otel-collector","service.version":"9.4.3"},"otelcol.component.id":"hostmetrics","otelcol.component.kind":"receiver","otelcol.signal":"metrics"}
{"level":"warn","ts":"2026-07-03T13:27:18.592Z","caller":"builders/builders.go:40","msg":"\"kubeletstats\" alias is deprecated; use \"kubelet_stats\" instead","resource":{"k8s.pod.name":"opentelemetry-kube-stack-daemon-collector-9rvr4","service.instance.id":"950b952c-3df6-46ed-aa60-e4c1ea57ce59","service.name":"elastic-otel-collector","service.version":"9.4.3"},"otelcol.component.id":"kubeletstats","otelcol.component.kind":"receiver","otelcol.signal":"metrics"}

This is now getting annoying. I would appreciate if these deprecation warnings get fixed as well AND the version containing the fix will not show new ones. Ideally there would be some CI/CD checks for things like this.

[infra-vault-gh-plugin-prod]

Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)

[swiatekm]

@elastic/ingest-otel-data could you have a look?

For clarity, this isn't an issue with the EDOT collector per se, but with our onboarding configuration. Otel upstream has embarked on a component renaming spree recently, and we haven't been updating. The warnings are largely harmless, but we should really catch this in K8s integration tests on otel dependency updates.

[hiSandog]

Given the upstream OpenTelemetry component renames, it would be useful to add a config lint or snapshot test for the onboarding values. The test could fail when deprecated aliases like hostmetrics or kubeletstats appear in generated collector config. That would catch these warnings before users see them after an operator upgrade.