Tyler Helmuth
Tyler Helmuth
@blakeromano is this issue related: https://github.com/open-telemetry/opentelemetry-helm-charts/issues/69
Hey @jacobwalters, can you clarify: are you are using the opentelemetry-collector chart or opentelemetry-operator chart?
> I am seeing that the operator creates a pvc that the collector pod is going to use Are you referring to the opentelemetry operator here?
I believe this issue is now superseded by https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/16519
Let's start by updating https://github.com/open-telemetry/opentelemetry-collector-releases/tree/main/distributions#criteria-for-supported-distributions
@astencel-sumo ya lets update `7` to say Windows MSIs are allowed. I forget the origin of that `brew` comment, but I believe it was calling out `brew` specifically as something...
Ya maybe this doesn't need updated because of that line, but I think if we're gonna support Windows, providing an MSI as an expectation (unless otherwise specified) makes sense.
@AlissonRS you're correct that the real fix is coming in an upcoming helm release. In the meantime, when using the collector chart as a subchart, I don't believe there is...
@AlissonRS no, the metrics pipeline will only get metrics data. Behind the scenes the otlpreceiver exposes endpoints like `v1/traces`, `v1/metrics`, and `v1/logs`. OTel SDKs sending traces will export to `v1/traces`,...
@jaronoff97 sounds good. I can dedicate cycles to this as well I think.