Skip to content

Helm Chart Assessments

Jump to bottom
Ivan P edited this page Jun 5, 2026 · 3 revisions

Structured assessment of each service's Helm chart, identifying the exact changes needed to support OTel, Pyroscope, and Faro configuration injection.

Status: In progress — Helm chart assessment prompt under development.

Approach

Each chart will be assessed using a dedicated prompt (similar to repo_otel_assessment_prompt.md) that examines the chart's structure and produces a consistent [CHART_NAME]_Helm_Assessment.md output covering:

  1. Chart overview — which Deployments/StatefulSets the chart manages, current env var injection approach
  2. OTel values additions — exact values.yaml additions for OTEL_SERVICE_NAME, OTEL_EXPORTER_OTLP_ENDPOINT, and any language-specific OTel flags
  3. Pyroscope values additions — PYROSCOPE_SERVER_ADDRESS and related config
  4. Faro values additions — opt-in faro.enabled / faro.proxy.* / faro.collectorUrl structure (where applicable)
  5. Sub-chart considerations — whether any Chart.yaml dependencies also require updates
  6. Diff-ready template snippet — exact changes to values.yaml and templates/deployment.yaml

Charts in Scope

Chart Services Managed Faro Applicable
acapy-agent chart acapy-agent No
acapy-vc-authn-oidc chart oidc-controller, frontend Yes
traction chart tenant-ui, ACA-Py plugin Yes
acapy-endorser-service chart endorser No
didwebvh-server-py chart didwebvh-server Yes
credo-ts consuming service chart host service Yes (consumers)
didcomm-mediator-credo chart mediator No
bc-wallet-demo chart server, frontend Yes

Assessments

(To be populated once the Helm chart assessment prompt is complete and run against each chart.)

Clone this wiki locally