Tyler Helmuth

I would argue the k8s distro is a better supervisor/collector combo since it is a production ready distro (we dont recommend using contrib in production) and because k8s is an...

I can help investigate this week

I believe the issue is using `tpl` inside `range`: https://github.com/helm/helm/issues/5979. @puckpuck @klucsik can you update the `Setup` step in `.github/workflows/lint.yaml` and `.github/workflows/demo-test.yaml` to use helm `3.14.4`

@puckpuck I'll wait to merge until you approve

Adding the specific images to the `values.yaml` is going to make it harder to keep up-to-date with the operator. I would much rather the operator be responsible for bumping the...

@ba1ajinaidu it looks like only your exporter is having trouble. Check that your endpoint/port is correct and available

Oh interesting. Can you add a debug exporter with `verbosity: detailed` to the pipeline and isolate it to only the troubled file?

And other logs flow through this pipeline to the same endpoint without issue? Can you point your OTLP exporter to a otlp receiver in another collector (or another pipeline in...

I think this could be achieved for any of our contexts by adding a new field when creating the TransformContext. I want to think more if it leaks abstraction tho....

Thought about this some more, I think in `NewTransformContext` the index can be calculated and stored as a private field on the struct and then a path could be made...