Tyler Helmuth
Tyler Helmuth
@snuggie12 I believe our PodDisruptionBudget feature was added before we supported StatefulSets. We're open to updating that template to supporting Statefulsets.
In the other charts we've started removing default resources and adding a warning to users to apply there our. We could follow that pattern here as well.
@szibis I'm not sure for what you are asking. What change would you like to see in the kube-stack helm chart?
Most of our charts dont set default resources but instead warn users if resources are not set. I'm not sure what the permissions of the ebpf agent are, can it...
Closed by https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/33508
Adding tracing caused performance issues, we need to look into why.
We'd still like a trace context so that we can include the trace and span ids in the debug logs context. Probably starting with a high-level trace for each call...
The rendering of the collector config supports templating. The final results is run through `tpl`. Is what you're trying not working?
The issue is that helm is not seeing your values.yaml as valid YAML, so it doesn't get past trying to read your input. The templating feature supports stuff like ```yaml...
This sounds like a good complex situation that the preset concept can help with. We need to make sure it stays opinionated - the presets should really only have boolean...