traversal-processor-charts Helm chart is versioned independently from the Traversal Processor container image (see Container image).
Breaking
The chart’s values layout was reorganized. Kubernetes deployment settings (replica count, image, resources, service, probes, scheduling, pod disruption budget) now sit at the top level of the values file, while processor-specific settings stay under the
traversalProcessor key. A few settings were also renamed, consolidated, or removed in the cleanup — for example, log ingestion is now configured through a single traversalProcessor.traversalIngestion.endpoint.Traversal builds and pre-populates your values file, so most deployments need no action. If you maintain your own overrides, re-check them against the updated values.yaml (helm pull … --untar) or the setup guide — some field names and locations have moved.Security
Client certificate material is now mounted from a Kubernetes Secret as a read-only file instead of being injected as a literal pod environment variable. No values file changes are required to pick up this fix. The same
mtls.certBase64/keyBase64 fields you already set are now delivered more securely under the hood.All customers should migrate to processorIngestion.endpoint going forward. It authenticates with the same mtls certificate as everything else.Metrics reporting is now on by default. The processor reports its own operational metrics to Traversal automatically; no configuration is required.