Tyler Helmuth

An [issue](https://github.com/open-telemetry/opentelemetry-collector/issues/10538) came up recently that wouldve been solved by the new transporterror type. Bumping this PR bc I'd like to see it merged.

@open-telemetry/helm-approvers please review as this is currently blocking the operator chart upgrade. I am most curious about the Istio solution of optionally including the CRDs in a template file via...

There are no plans to allow the operator chart to install CRs, that will be the work of the `opentelemetry-kube-stack` chart.

Also we'll need to think about how these changes will affect that chart

@jaronoff97 that seems reasonable, but I'm confused about the comparison to `kube-prometheus-stack`. It looks like `kube-prometheus-stack` made a subchart within `kube-prometheus-stack` so that others cant use it directly. Are you...

If we follow the pattern set by in `kube-prometheus-stack` we'd eventually deprecate the operator chart in favor of only `opentelemetry-kube-stack`. If that ends up being the case, we wouldnt need...

> I'm in favor of doing 1, because we have some consumers of the operator chart who want to depend on it while also shipping otel CRs, and it would...

This issue is still waiting for the new extension to mature

The operator chart cannot include the same preset concept as the collector chart since it does not install OpenTelemetryCollector CRs. The Operator, and now its chart, do have better support...

@haseeb-aziz that error message is normally hiding a deeper issue. I've seen it when not being able to communicate properly with the grpc endpoint I'm trying to send data to....