Tyler Helmuth
Tyler Helmuth
I was only able to reproduce this issue on chart version 0.14.1 if `tag` is set to `latest`. If `tag` is `0.48.0` then I could install your values.yaml as expected....
Hello @caibirdme, can you expand on what you mean? LivenessProbe and readinessProbe ports are normally not exposed in the deployment/daemonset's `ports` section. [You can see both probes working as expected...
@dmitryax Is this something to address after/during the refactor referenced in #91
@dmitryax Gonna take a look at this now
> @TylerHelmuth yes, this one will be resolved after the chart configuration interface restructuring #91 Ok I will hold off then.
If you want a gateway deployment of the collector then I think the [standaloneCollector](https://github.com/open-telemetry/opentelemetry-helm-charts/tree/main/charts/opentelemetry-collector#default-configuration) settings are what you want. The standalone collector is a single deployment of the collector within...
Does `opentelemtry-otlp` already add the signal path automatically when using gRPC?
You're totally right, my bad
@Aneurysm9 @bryan-aguilar please review, thanks!
The reason it isn't included by default in that example, and why it isn't included by default in the [collector helm chart](https://github.com/open-telemetry/opentelemetry-helm-charts/tree/main/charts/opentelemetry-collector), is that it requires [extra permissions](https://pkg.go.dev/github.com/open-telemetry/opentelemetry-collector-contrib/processor/k8sattributesprocessor#hdr-RBAC). Requiring elevated...