Tyler Helmuth

I am certainly interested in this if users are interested in this. A couple questions: 1. @jaronoff97 if this chart was accepted, would you be available as a CodeOwner for...

@jaronoff97 I'm also curious if your chart handles the installation of the operator and the OpentelemetryCollector object like discussed here: https://github.com/open-telemetry/opentelemetry-helm-charts/issues/69

@jaronoff97 sounds good. @open-telemetry/helm-approvers please add your thoughts.

I also see value in a "transition" chart. Long term (like long long term), I think a need for a chart like this diminishes, but for users today who have...

Could also be cool to include somewhere how to grab the same telemetry using the collector and its components.

@dmitryax is there anything else we're waiting on before accepting PRs adding this chart?

For the cert manager my preference would be to copy whatever pattern kube-prometheus-stack is using. If we can't install the cert manager as part of the chart install that will...

Seeing as the chart is trying to follow the same pattern for value I think it makes sense to follow the same technical patterns as well.

@kalpesh6331 what collector image are you using? As this isn't specific to the helm chart I'll move the issue to the appropriate repository once I know what image you're using.

Similar to https://github.com/open-telemetry/opentelemetry-collector-releases/issues/357 we show hold off until we have split up our CI. I am very close to a solution, right now I'm waiting on goreleaser-pro 1.24 which has...