fix(chart): bump opentelemetry-collector subchart 0.52.* -> 0.165.0 - #544
Merged
Conversation
The 0.1.15-rc-1 dev-gke rollout caught the collector 0.156.0 pod failing config parse: the 0.52-era subchart injects defaults removed from modern collectors — the memory_ballast extension, the logging exporter, and service.telemetry.metrics.address. The old 0.75.0 ReplicaSet kept serving, so dev stayed up; the new pod could not start. Bump the subchart to 0.165.0 (the chart release paired with app 0.156.0). Its defaults use the debug exporter, drop memory_ballast, and emit current telemetry keys. Our values overlay (mode, image, ports, config with the clickhouse exporter) is schema-compatible unchanged. Verified: helm dependency update + helm template, then `otelcol-contrib validate` from the actual 0.156.0 image against the FULL rendered collector ConfigMap — exit 0 (previous validation only covered our exporter block, which is how the subchart-default breakage slipped to the RC stage). Chart 0.1.15 -> 0.1.16.
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the Chart.yaml for the nudgebee-agent Helm chart. It increments the chart version to 0.1.16 and updates the opentelemetry-collector dependency version from 0.52.* to 0.165.0. There are no review comments, and I have no feedback to provide.
RamanKharchee
approved these changes
Jul 17, 2026
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
The
0.1.15-rc-1dev-gke rollout caught the collector 0.156.0 pod failing config parse — the RC stage doing its job. Root cause: the0.52.*-era subchart injects defaults that modern collectors removed:The old 0.75.0 ReplicaSet kept serving, so dev stayed up.
Fix: subchart →
0.165.0(the chart release paired with app 0.156.0): defaults usedebug, nomemory_ballast, current telemetry keys. Our values overlay (mode,image,ports,configincl. the clickhouse exporter) is schema-compatible unchanged.Verified
helm dependency update+helm template, thenotelcol-contrib validatefrom the actual 0.156.0 image against the full rendered collector ConfigMap → exit 0Chart
0.1.15→0.1.16.How Has This Been Tested?
0.1.16-rc-1→ dev-gke redeploy after merge — confirm the new collector pod replaces the 0.75.0 ReplicaSet and logs/traces land in clickhouse