[chore] Additional Helm chart and Terraform configurability - #15
Closed
kylehounslow wants to merge 1 commit into
Closed
kylehounslow wants to merge 1 commit into
kylehounslow wants to merge 1 commit into
Conversation
kylehounslow
force-pushed
the
feat/eval-backend-enablement
branch
2 times, most recently
from
June 24, 2026 17:09
cf6ed96 to
ff46c04
Compare
… sizing Add chart and terraform configurability for running the stack at varied scale and with custom Data Prepper routing: - dataPrepperManageSecret (default true): when false, the chart skips rendering the pipeline Secret so you can supply your own (same name) with custom routing/sinks via data-prepper.pipelineConfig.existingSecret. Default preserves current behavior. - data-prepper-metrics-service: publish DP's 4900 metrics port on its own ClusterIP Service (the subchart puts 4900 on the pod but not the Service); point the collector scrape at it. Gated on data-prepper.enabled. Fixes empty DP panels on the pipeline-health dashboard. - dataPrepperTraceFlushInterval (default 180, the upstream default): parameterize the otel_traces processor flush window. - terraform sizing knobs: opensearch replicas/storage/memory/heap, cortex storage, data-prepper memory/heap/flush-interval. JVM heap vars validate JVM size syntax. Defaults unchanged from prior behavior. Chart version 0.2.0 -> 0.3.0. Signed-off-by: Kyle Hounslow <kylhouns@amazon.com>
kylehounslow
force-pushed
the
feat/eval-backend-enablement
branch
from
June 24, 2026 17:44
ff46c04 to
6d92bb2
Compare
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
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.
Summary
Adds chart and Terraform configurability for running the stack at varied scale and with custom Data Prepper routing. All defaults preserve current behavior; this is additive configurability, not a behavior change.
Changes
dataPrepperManageSecret(defaulttrue): whenfalse, the chart skips rendering the Data Prepper pipeline Secret, so you can supply your own (same name) with custom routing/sinks viadata-prepper.pipelineConfig.existingSecret. Lets operators with non-default ingest topologies own the pipeline config without forking the chart.data-prepper-metrics-service: publishes Data Prepper's 4900 metrics port on its own ClusterIP Service. The subchart puts 4900 on the pod but not on a Service, so the collector scrape was refused and the pipeline-health dashboard's DP panels stayed empty. Gated ondata-prepper.enabled; collector scrape points at the new Service.dataPrepperTraceFlushInterval(default 180, the upstream default): parameterizes theotel_tracesprocessor flush window.2g, not2Gi). Defaults unchanged.0.2.0->0.3.0.Testing
helm lintclean;helm templateconfirms themanageSecretgate toggles the Secret on/off and the metrics Service only renders when Data Prepper is enabled.terraform validatepasses; heap-suffix validation rejects2Gi.