Tyler Helmuth

We talked a little about this topic in https://github.com/open-telemetry/opentelemetry-collector-releases/issues/429. In my opinion we should be releasing each distro with its own tag push, instead of releasing all distros based on...

We should add it to the k8s distro as well since it is an OTLP receiver/exporter

It isn't much work to add the extra artifacts to the release. We originally started with them but slimmed it down during PR discussions.

Saw that Database semconv was getting ready to mark stable and I love that this has existed along side it ❤️

I spent time thinking about this as well and haven't come up with a better solution that a field on the struct for how to give component access to the...

@mx-psi the [batchprocessor](https://github.com/open-telemetry/opentelemetry-collector/blob/18d5c02ade6f41f2cf8d01d3fa7a0fb8f97534a8/processor/batchprocessor/metrics.go#L51) uses it to check [later](https://github.com/open-telemetry/opentelemetry-collector/blob/18d5c02ade6f41f2cf8d01d3fa7a0fb8f97534a8/processor/batchprocessor/batch_processor.go#L411-L413) if it should calculate a value. The other is otelarrow, doing similar checks to see if if should do some math. The...

I got this on the 0.123.0 release.

I agree we should support this. @mterhar for a work around, what happens if you do: ```yaml service: telemetry: resource: pod_ip: "my favorite ip" ```

For now you can use env vars and downard API. I believe something like this will work: ```yaml mode: deployment image: repository: otel/opentelemetry-collector-k8s extraEnvs: - name: K8s_POD_NAME valueFrom: fieldRef: fieldPath:...

@Uncle-Justice you linked to a PR that is in a non-opentelemetry organization. I'm not sure what the issue is that you're trying to fix. We try not to add kubernetes-specific-version...