Consider having the k8sattributesprocessor in the default configuration for Collector Getting Started with K8s

[cartermp]

This was discussed in #370

Today, we point at a manifest that doesn't have the k8sattributesprocessor. It's a very valuable processor that people are likely to use when in the context of k8s.

Currently, the file we recommend pulling in lives in the upstream collector repo. So if that file were to change, it'd have to include the processor. Otherwise, we'd have to consider a different command to get started with.

[svrnm]

You mean https://raw.githubusercontent.com/open-telemetry/opentelemetry-collector/main/examples/k8s/otel-config.yaml ?

That issue should then be raised with the collector repo?

[TylerHelmuth]

The reason it isn't included by default in that example, and why it isn't included by default in the collector helm chart, is that it requires extra permissions. Requiring elevated permissions in a default scenario gets kinda tricky.

[cartermp]

Hmm, in that case, would it be helpful to have a subsection in there that tells you how to use the processor and then specify which permissions you need to do so?

[TylerHelmuth]

Sure, the processor's documentation has a good RBAC section to help users. Should be able to link to that.