Backlog triage: 25 open issues are closable today (status review of all 101 open issues)

[marcschaeferger]

What this is

A triage pass over every open issue in this repository — repo:open-telemetry/opentelemetry-helm-charts is:issue is:open, 101 issues, snapshot 29 August 2026, checked against main at f2a0e6e.

The intent is to give maintainers one place to approve a backlog cleanup. Assisted by AI for Data Retrieval BUT manual reviewed and adjusted

How this list was produced

• All 101 open issues were enumerated from GitHub Search for the scoped query above; pull requests were followed as evidence but are not counted as issues.
• Every linked PR was opened individually to confirm that it is actually merged (not merely referenced) and to record the merge date.
• The claimed result was verified against main at f2a0e6e values files, templates, and examples. Not relying on PR Description.
• The triage was compiled with AI assistance and rechecked against the repository by hand; please treat it as a proposal for maintainer review rather than a verdict.

Result at a glance

Group	Category	Count	Proposed action
A	Implemented by a merged PR	13	Close now
B	Resolved, answered, or explicitly not planned	7	Close now
C	Duplicate	1	Close now
D	Superseded by an upstream tracker or by current chart policy	4	Close now
E	Close after a short maintainer confirmation	2	One scoped call each
F	Belongs in opentelemetry-operator, not in the charts	3	Move / close in favour of upstream
G	Stale support thread, no chart-side reproduction	6	Maintainer review, then close
H	Needs info / needs a current reproduction	7	Ask for a repro, close if none
	Subtotal — actionable	43
I	KEEP — active work, an open PR, or an unresolved request	58	No action proposed
	Total open issues	101

25 issues (groups A–D) are closable today

---

A. Implemented by a merged PR - close now (13)

Issue	Short title	Implemented by	Verified on current main
#697	Support configuring and disabling the healthcheck extension	#798 (merged 2023-06-01)	Configurable liveness/readiness probes are present
#964	eBPF CI scenarios	#1310 (merged 2024-08-27)	Close rationale already commented — just close
#1111	Add automountServiceAccountToken to the deployment	#1707 (merged 2025-06-18)	Value + Deployment/ServiceAccount rendering present
#1349	Grant the eBPF k8s collector job-watching permission	#1346 (merged 2024-09-26)	jobs permission in the ClusterRole
#1401	Invalid runbook URLs	#1736 (merged 2025-07-10)	Close rationale already commented — just close
#1453	Prometheus presets not working due to templating	#1455 (merged 2024-12-12)	Missing ServiceMonitor scrape-limit helper added
#1604	Missing revisionHistoryLimit	#1658 (merged 2025-05-05)	revisionHistoryLimit: 10 in values, rendered
#1637	Label values over 63 characters	#1558, #1778, #1790 (all merged)	Close rationale already commented — just close
#1703	Add a new eBPF instrumentation Helm chart	#1704 (merged 2025-10-31)	charts/opentelemetry-ebpf-instrumentation incl. CI + examples
#1916	Add a kubernetesObjects preset	#2196 (merged 2026-05-21)	presets.kubernetesObjects incl. RBAC
#1943	CRD-less Operator-chart example	#2265 (manager-config support)	charts/opentelemetry-operator/examples/manager-config/values.yaml
#2103	Add minReadySeconds support	#2190 (merged 2026-05-12)	minReadySeconds: 0 in values, rendered
#2216	hostmetrics exclusion uses glob syntax in a regexp	#2217 (merged 2026-06-04)	Patterns replaced with valid regular expressions

B. Resolved, answered, or explicitly not planned - close now (7)

Issue	Short title	Why it can be closed
#1055	Components missing when executed through the chart	Image/OCB-config mismatch, not a chart defect; the reporter confirmed the diagnosis
#1163	OTel Collector container not running	Reporter confirmed it is fixed with opentelemetry-collector-contrib:0.125.0
#1339	invalid argument after the 0.69.0 upgrade	Feature-gate bug fixed in Operator v0.110.0; the remaining symptom was drift from upgradeStrategy: none under GitOps reconciliation
#1506	Cannot enable auto-instrumentation for Go	Supported today via manager.extraArgs: [--enable-go-instrumentation]; the reporter resolved it that way
#1581	Need help defining an Argo CD application for the collector chart	The chart-discovery question was answered; the repository-URL behaviour is tracked in #1766
#1672	Mounting /var/lib/docker/containers seems useless	Explicit maintainer decision: keep the mount until Kubernetes drops the compatibility path → close as not planned
#1935	service.telemetry.metrics decoding failed	Reproduced successfully on current releases; the report used kube-stack 0.6.2 and this project does not backport chart fixes

C. Duplicate - close now (1)

Issue	Short title	Canonical issue
#2166	404 when pulling without adding the repository	Duplicate of #1766 — same reproduction, same behaviour

D. Superseded by an upstream tracker or by current policy - close now (4)

Issue	Short title	Where the work belongs
#1381	reinvocationPolicy: IfNeeded	open-telemetry/opentelemetry-operator#3349 — the API and admission-webhook change must land there before a chart value makes sense
#1757	Increase Operator memory limits	Superseded by policy: #1457 removed the fixed Operator resource defaults and kube-stack does not override them, so deployments set opentelemetry-operator.manager.resources themselves
#1996	Missing liveness/readiness probes in the Operator-managed Collector	open-telemetry/opentelemetry-operator#4220 — controlled by the Operator reconciliation path
#2114	A new chart without CRDs	Covered by the existing Operator chart plus the manager-config support from #2265 (crds.create: false, ignoreMissingCollectorCRDs: true)

---

E. Close after a short maintainer confirmation (2)

Issue	Short title	What is already true	The one call to make
#1555	Operator Service annotations / topology	Service annotations are supported via manager.serviceAnnotations (or opentelemetry-operator.manager.serviceAnnotations through kube-stack)	Is the later, broader "arbitrary Service spec fields" request in scope here, or should it be a focused follow-up?
#1879	Demo default configuration	#1880 fixed the missing parameters and dashboards; demo chart 0.40.0 / Demo 2.2.0 was expected to resolve the report	No explicit reporter confirmation followed — ask for one final verification before closing

F. Belongs in opentelemetry-operator, not in the charts (3)

These cannot be fixed chart-side; the chart can only expose what the OpenTelemetryCollector API offers.

Issue	Short title	Why it must move
#696	Collector imagePullSecrets	A maintainer already explained that the field has to be exposed by the OpenTelemetryCollector API first
#1547	Presets in the Operator CRD	Requires an Operator CRD/API and reconciliation design decision, not chart rendering
#1646	Override the OpAMP bridge CLI arguments	The argument belongs to the CR/API; a maintainer suggested moving the request upstream

G. Stale support threads without a chart-side reproduction (6)

Suitable for a short maintainer review and then closure with a "please reopen with a current reproduction" comment — not for automatic closure.

Issue	Short title	Reason
#646	http2 frame too large	Long thread of environment-specific protocol/certificate/endpoint/port fixes; no reproducible chart defect remains
#775	External Secrets mounts	The supported approaches using existing Secrets/subchart configuration are documented in the thread; no unresolved defect
#1068	OTLP logs not exposed	Old configuration-support thread, no current minimal reproduction
#1087	Airflow integration	Integration discussion with working example configuration, not a chart defect
#1513	kubeletstats x509 error	Troubleshooting path is known; needs a secure current TLS reproduction rather than dismissal
#1618	Internal Collector metrics	Maintainers could not reproduce it and the reporter had no minimal reproduction

H. Needs info / needs a current reproduction (7)

Proposal: label these needs-info, ask the reporter for a current-version reproduction, and close if nothing arrives within the usual stale window.

Issue	Short title	What is missing
#1332	filelog mount points	No maintainer resolution and no current reproduction
#1590	extraVolumeMounts mount path	No current reproduction
#1626	Canonical auto-instrumentation image	Needs a current owner and a compatibility decision
#1702	Custom TLS certificate values	Needs a current reproduction
#1770	Rocky Linux eBPF support	Platform compatibility needs an active tracker or a current report
#1902	Argo Rollouts discussion	No closure evidence either way
#2161	Restart on an invalid certificate	Current reproduction required

---

I. Guardrails - issues that look closable but must stay open

Listed explicitly because superficial evidence (a linked PR, a duplicate marker) points the wrong way here.

Issue	Why it stays open
#905	The linked Collector Contrib issue #27261 was closed in favour of this issue, and its implementation PR (contrib#37114) was closed unmerged. This is the canonical Helm-chart tracker — do not close it.
#929	#1721 was closed unmerged; no CI example has been shown to exist
#1365	#1368 was closed unmerged and the eBPF template still needs a privileged security context
#1469	#1521 was closed unmerged and the related upstream work is unresolved
#1600	#1573 did not cover the requested example generation, as stated in the discussion
#1824	The duplicate event points at #2261, but #1824 is the canonical issue — keep this one
#2183	Some rename PRs are merged, but current charts still rewrite the old k8sattributes names; the issue intentionally tracks deprecation/removal
#2209	#2329 merged only intermediate steps; its own description says later steps remain
#2231	Possibly related to certificate recreation, but not proven to be a duplicate of #2168
#2245 / #2255 / #2370	Active implementation PRs: #2322, #2343, #2369

The remaining KEEP issues (58 in total) have active work, an open PR, or an unresolved product request, and are not part of this proposal.

---

Overview

• P0 — Group A, implemented by merged PRs: Support configuring and disabling healthcheck extension #697, add automountServiceAccountToken to deployment #1111, Grant ebpf k8s collector job watching permission #1349, [opentelemetry-kube-stack]: Prometheus presets not working due to templating #1453, [opentelemetry-operator] Missing revisionHistoryLimit #1604, [opentelemetry-ebpf-instrumentation] add new helm chart #1703, [opentelemetry-collector]: add kubernetesObjects presets #1916, Create an example in the operator chart for crd-less approach #1943, feat(opentelemetry-operator) Add minReadySeconds support for operator deployment #2103, [opentelemetry-collector, opentelemetry-kube-stack] hostmetrics mount point excludes use glob syntax in regexp match #2216
• P0 — Group A, close rationale already commented, nothing to add: Add CI scenarios for eBPF Chart #964, [collector] prometheus rule runbook urls are invalid #1401, Labels value exceeds character limit of 63 when name of the namespace is big #1637
• P0 — Groups B + C, resolved / answered / not planned / duplicate: components missing when executes through chart #1055, OTel Collector Container not running #1163, invalid argument issue after 0.69.0 upgrade #1339, Helm "opentelemetry-operator" - cannot enable auto instrumentation for Golang #1506, Need help defining argocd application using otel-collector chart #1581, Mouting /var/lib/docker/containers seems useless #1672, service.telemetry.metrics decoding failed - '' has invalid keys: address #1935, 404 not found when pulling without adding repo on helm #2166
• P1 — Group D, upstream trackers and the resource-default policy: reinvocationPolicy: IfNeeded #1381, [kube-stack] Increase opentelemetry-operator resource memory limits #1757, [opentelemetry-kube-stack] LivenssProbe not showing up on collector pods, even it is set in values.yaml of kube-stack helm chart and operator creates daemonSet #1996, Create a new helm chart using the autoinstrumentation capabilities of the operator without CRDs #2114
• P2 — Group E, one scoped maintainer call each: Add/Modify Annotations for Service in Operator chart - support Topology Aware Routing #1555, OpenTelemetry demo chart default config not working correctly #1879
• P2 — Groups F + G, API spillover and stale support threads: imagePullSecrets on the collector image #696, Add presets in OpenTelemetryCollector CRD of OpenTelemetry Operator #1547, Is there any way to override OpAMPBridge CLI values? #1646, desc = "error reading server preface: http2: frame too large" #646, [collector] How to use external secrets to for secret mounts. #775, OTLP Receiver in Kubernetes Cluster Not Exposing Logs #1068, opentelemetry helm charts is not straightforward for Airflow[otel] integration #1087, kubeletstats: failed to verify certificate: x509 error #1513, [opentelemetry-kube-stack] enabling internal metrics of collectors #1618
• P3 — Group H, ask for a current reproduction: Filelog receiver log mount points #1332, extraVolumeMounts in opentelemetry-collector chart is not creating mount path #1590, [opentelemetry-kube-stack] canonical way to change image for autoinstrumentation #1626, [Opentelemetry-operator] Provision a TLS Certificate for the OpenTelemetry Operator with a values file #1702, Rocky Linux not detected as supported distribution #1770, feat/argo-rollout discussions #1902, [Operator] Cert invalid after cluster restart #2161