Mike Dame

Could you define it as a [volume](https://github.com/open-telemetry/opentelemetry-operator/blob/e66ef73/apis/v1alpha1/opentelemetrycollector_types.go#L132) and then override `--config` with [args](https://github.com/open-telemetry/opentelemetry-operator/blob/e66ef73/apis/v1alpha1/opentelemetrycollector_types.go#L57)? I'm also interested in if offering more ways to pass config has been considered. For one use...

One use case could be a centralized spot for configs when running multiple collectors. It also enables patching, at least with local yaml config files. In general it's a common...

Working on a poc for this /assign

Opened a PR at https://github.com/open-telemetry/opentelemetry-operator/pull/1240, ptal

@a7i you mean different events than k8s events?

This will be available as a [DefaultEvictor config](https://github.com/kubernetes-sigs/descheduler/blob/a7113dab5048c556046fb61addd2ce84f9760094/README.md#evictor-plugin-configuration-default-evictor) in the v1alpha2 config api release, so we should be able to close this (https://github.com/kubernetes-sigs/descheduler/pull/929, https://github.com/kubernetes-sigs/descheduler/pull/955) /close

@a7i do you think we should revive this? at least mark as frozen, it came up in slack

@MrAlias is this closed by https://github.com/open-telemetry/opentelemetry-go-instrumentation/pull/708?

Going through https://opentelemetry.io/docs/specs/semconv/http/http-spans/#http-client-server-example: # Name > HTTP spans MUST follow the overall [guidelines for span names](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.26.0/specification/trace/api.md#span). > HTTP server span names SHOULD be {method} {http.route} if there is a (low-cardinality)...

I'll have to try again and update here. It's possible that the environment didn't have ebpf enabled. This isn't a high priority bug, more of a question of if anyone...