> ## Documentation Index
> Fetch the complete documentation index at: https://docs.traversal.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Processor Helm chart changelog

> What's new in each traversal-processor-charts release, and any migration notes for upgrading.

The `traversal-processor-charts` Helm chart is versioned independently from the Traversal Processor container image (see [Container image](https://docs.traversal.com/setup/processor.md#container-image)). Earlier releases are not listed.

**0.9.1**

**Startup configuration logging.** Each pod logs its effective configuration at startup,
including ports, size-preset tuning, endpoints, TLS and mTLS credential sources, and
configuration source. Credentials are not logged. See
[Startup logging](https://docs.traversal.com/setup/processor.md#startup-logging).

**Overridden settings logging.** A startup line lists every setting supplied through the
environment, by variable name and source. It does not log the values. See
[Overridden settings](https://docs.traversal.com/setup/processor.md#overridden-settings).

**Throughput logging improvements.** Throughput lines report rates over the interval since
the previous line, show whether the processor is rejecting data or failing to send it to
Traversal, and are followed by the systems the processor is receiving the most data from. See
[Throughput logging](https://docs.traversal.com/setup/processor.md#throughput-logging).

**Log level setting.** The `traversalProcessor.logLevel` value sets the processor's log level.
The chart default is empty, and the processor runs at `info`. See
[Log verbosity](https://docs.traversal.com/setup/processor.md#log-verbosity).

**Telemetry forwarder probes.** The telemetry forwarder container has exec liveness and
readiness probes, so clusters that enforce probes on every container admit the pod.

**SQS adapter image update.** The SQS adapter defaults to image `0.1.1`.

Requires processor image `0.8.0` and defaults to it.

**0.8.2**

**Splunk HEC endpoint.** The processor accepts Splunk HTTP Event Collector (HEC) requests at
`/services/collector` on the main ingest port, using Splunk's batch formats, authentication
forms, and response codes. No chart configuration is required. See
[Splunk HEC](https://docs.traversal.com/setup/processor.md#splunk-hec).

**Compressed OTLP requests.** The OTLP gRPC and HTTP endpoints accept gzip-compressed requests,
which the OpenTelemetry Collector and SDKs send by default.

**Throughput logging.** When `traversalProcessor.logThroughput` is `true`, each pod logs its
uptime and ingest totals about once a minute. Throughput logging is off by default. See
[Throughput logging](https://docs.traversal.com/setup/processor.md#throughput-logging).

Requires processor image `0.7.2` and defaults to it. With an older `image.tag`, the HEC
endpoint and OTLP compression are unavailable.

**0.8.1**

**More efficient configuration delivery to the processor.** No chart configuration changes are
required.

Defaults to processor image `0.7.1`.

**0.8.0**

**Redaction rules move to the processor configuration.** This chart removes
`traversalProcessor.redaction`, including `rulesContent` and `existingConfigMap`, and the
ConfigMap the chart rendered from it. Redaction rules are now part of the configuration that
Traversal publishes to the processor, alongside field extraction settings. Rule changes take
effect on the next configuration refresh, without a restart or redeploy.

> [!WARNING]
>
> If your values set `traversalProcessor.redaction`, contact Traversal to move your rules
> into the processor configuration before you upgrade. The upgrade removes the mounted rules file,
> and no data is redacted until the rules are moved.

Values that do not set `traversalProcessor.redaction` are unaffected.

Requires processor image `0.7.0` and defaults to it. Earlier images do not read rules from the
processor configuration, so redaction is off if you pin an older `image.tag`. See
[Redaction](https://docs.traversal.com/setup/redaction.md).

**0.7.0**

**Single base domain for Traversal endpoints.** The new `traversalProcessor.baseDomain` value
sets the domain of all Traversal endpoints, and the chart derives the ingest, configuration, and
telemetry URLs from it. Explicitly set endpoints override the derived values, so existing values
are unaffected. See [Endpoints](https://docs.traversal.com/setup/processor.md#endpoints).

**Telemetry follows `baseDomain`.** Ingest and telemetry endpoints are resolved independently, so
setting only the ingest URL leaves telemetry on Traversal's hosted endpoints. Setting `baseDomain`
moves all endpoints together.

**Resolved endpoints in install output.** The install output lists the endpoints that the release
resolved. It can also include advisory notes about your values: missing field configuration, a
missing client certificate, an account ID that is not a UUID, or unrecognized keys directly under
`traversalProcessor`, such as typos or settings from an older values layout.

These notes do not cause an install to fail. They describe only your values: `extraEnv` and
`extraEnvFrom` can override what the chart writes, so a deployment configured through those values
can be correct even when a note appears. Nested keys and `extraEnv` variable names are not
checked. A release that does not resolve an ingest endpoint still fails the install.

Defaults to processor image `0.6.0`.

**0.6.0**

**PEM certificate fields.** The new `traversalProcessor.mtls.certPEM` and
`traversalProcessor.mtls.keyPEM` values accept PEM content directly, and the chart base64-encodes
it. Use them with `--set-file` to pass certificate files from disk. The ingest TLS block adds the
equivalent `tls.certPEM` and `tls.keyPEM` values. See
[Required values](https://docs.traversal.com/setup/processor.md#required-values).

**Install-time validation of certificate encoding.** If a base64 field contains PEM content, the
install fails with an error that names the correct field. Previously, the chart rendered without
errors, and the value was later rejected by the Kubernetes API server or caused the processor to
crash on an unreadable certificate.

**mTLS private key removed from the pod environment.** Inline credentials are read from the
mounted Secret, as `existingSecret` credentials already were. The key is no longer visible to
anyone who can read the pod definition.

**Operational counters.** The processor reports operational counters to Traversal with each
configuration fetch, including ingest volume, request and drop counts, and how recently its
configuration was updated. Reports contain only counters and identifiers, not log content,
keyword values, or configuration values.

Existing values require no changes. `certBase64`/`keyBase64` and `certB64`/`keyB64` are
still supported, and pre-encoded values are used as before. The upgrade restarts the processor
once to apply the new certificate configuration.

Defaults to processor image `0.6.0`.

**0.5.0**

**Log ingestion from Amazon SQS.** The processor can ingest logs from an Amazon SQS queue
without a separate forwarder service. It is off by default, so existing deployments are
unaffected until you enable it. See
[Log ingestion from Amazon SQS](https://docs.traversal.com/setup/processor.md#log-ingestion-from-amazon-sqs).

**More predictable memory usage when output latency spikes.** A slow or briefly unavailable
output endpoint now applies backpressure instead of growing the processor's memory. No
configuration changes are required.

Defaults to processor image `0.5.0`. The SQS adapter defaults to image `0.1.0`.

**0.4.1**

**Telemetry forwarder sidecar.** The chart adds an Alloy sidecar container that buffers the
processor's own telemetry and forwards it to Traversal. It is on by default. The chart fails to
render unless you supply an mTLS source: a Secret (inline `traversalProcessor.mtls.certBase64`
and `keyBase64`, or `traversalProcessor.mtls.existingSecret`), or file paths together with
`extraVolumeMounts`. Set `traversalProcessor.observability.otel.sidecar.enabled` to `false` to
opt out. See [Telemetry forwarding](https://docs.traversal.com/setup/processor.md#telemetry-forwarding).

**Existing Secret for mTLS material.** You can point the processor at an existing Kubernetes
Secret with `traversalProcessor.mtls.existingSecret`. Inline base64 and PEM file paths
(`mtls.certFile`, `mtls.keyFile`) were already supported.

**Self-reported metrics can egress through a forward proxy.** If outbound traffic from your
cluster must pass through a proxy, the processor's own operational metrics can be routed
through it.

**More stable memory usage.** Internal ingest memory budgets are adjusted based on the `size`
preset to make memory usage more predictable.

Defaults to processor image `0.4.0`.

**0.4.0**

**Reorganized values layout.** Kubernetes deployment settings (replica count, image, resources,
service, probes, scheduling, pod disruption budget) now sit at the top level of the values,
while processor-specific settings stay under the `traversalProcessor` key. Some settings were
renamed, consolidated, or removed. For example, log ingestion is now configured through a single
`traversalProcessor.traversalIngestion.endpoint`.

**Size presets.** The `traversalProcessor.size` value selects a validated resource and tuning
preset. See [Sizing and throughput](https://docs.traversal.com/setup/processor.md#sizing-and-throughput).

**Datums sink replaces Kinesis.** The processor sends data to Traversal through the v2 datums
sink instead of Kinesis. If you upgrade from a 0.3.x chart, check your ingest settings against
the new `values.yaml`.

If you maintain your own overrides, re-check them against the updated `values.yaml`
(`helm pull … --untar`) or the [setup guide](https://docs.traversal.com/setup/processor.md). Some field names and locations
have moved.

Defaults to processor image `0.4.0`.

**0.2.1**

**Client certificate delivered as a read-only file.** Client certificate material is mounted
from a Kubernetes Secret as a read-only file instead of being injected as a literal pod
environment variable. No values changes are required. The same `mtls.certBase64` and
`mtls.keyBase64` fields you already set are delivered more securely.

Defaults to processor image `0.2.6`.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.