Tyler Helmuth

Sure. I'm most interested in ensuring that the data the the 2 separate routers were intending to capture really can be capture by the same router.

This doc may also be helpful: https://opentelemetry.io/docs/collector/scaling/

Yes we can provide a default value for these, although instead of specifying the image version in the values.yaml we should really be using the appVersion.

What version of the operator and operator helm chart are you using?

Also are you supplying a values.yaml? I was able to install the open-telemetry/opentelemtry-operator chart on a cluster with cert-manager without issue.

@jaingaurav03 I ran ``` kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.12.0/cert-manager.yaml helm repo update helm install testing open-telemetry/opentelemetry-operator ``` Make sure that you wait long enough for the cert-manager to be fully up...

You can currently configure `image.pullPolicy` in your values.yaml. The default value is `IfNotPresent`. I don't see anything in https://kubernetes.io/docs/concepts/containers/images/#imagepullpolicy-defaulting recommending to always use `Always`. Since we specify a image version...

Please bump the chart patch version and run `make generate-examples CHARTS=opentelemetry-collector`

> new version bump? Looks like you took care of it

The current operator chart does not install any `OpenTelemetryCollector` custom resources, which is where a preset like `kubernetesAttributes` would be useful. When using the `opentelemetry-operator` chart, you must install `OpenTelemetryCollector`...