Alex

@jascsch Can you provide some context on what you are trying to do ? There is a bit of confusion on why the installation of the operator chart does not...

@jascsch can you share the helm command you use to install the opentemetry-operator chart ? I'm not sure why the error mentions the `opentelemetry-collector` chart and not the operator. Also...

> helm upgrade --install opentelemetry-operator -f values.yaml -n opentelemetry open-telemetry/opentelemetry-collector --debug You need to replace `open-telemetry/opentelemetry-collector` with `open-telemetry/opentelemetry-operator` as indicated in the [DOCS](https://github.com/open-telemetry/opentelemetry-helm-charts/tree/main/charts/opentelemetry-operator#install-chart)

@MarkAndersonTrocme pls bump the chart version. Also I would tend to give a bit more memory for limits.

We increase the minor version and maybe update the main Readme with a warning? While the chart suggests sensible defaults users are responsible for setting their own resource allocation values....

@TylerHelmuth @dmitryax I've reopened this as I think it's useful to set lower sensible defaults. PTAL

@TylerHelmuth I might be able to take this one but for a limited set of use cases I've tried . I might add once we roll out more internally.

@dmitryax yeah, I'd be interested in that. Who would be the second sponsor?

Opened https://github.com/open-telemetry/community/issues/1100 . Thanks guys.

@TylerHelmuth I'm not sure our use cases are something other users would appreciate as we run the operator/collector on clusters which we are not admins on so clusterrole/webhooks need to...