fix(helm): sync chart with Docker Compose (3.7.0, scrape labels, SYNC.md)#244
Open
ps48 wants to merge 2 commits into
Open
fix(helm): sync chart with Docker Compose (3.7.0, scrape labels, SYNC.md)#244ps48 wants to merge 2 commits into
ps48 wants to merge 2 commits into
Conversation
….md) Signed-off-by: ps48 <pshenoy36@gmail.com>
joshuali925
approved these changes
May 12, 2026
| endpoint: "{{ .Release.Name }}-data-prepper:21890" | ||
| tls: | ||
| insecure: true | ||
| insecure_skip_verify: true |
Member
There was a problem hiding this comment.
do we need to add a warning in readme that production stacks should verify tls?
joshuali925
reviewed
May 12, 2026
| 3. Did a pipeline change in `docker-compose/data-prepper/pipelines.template.yaml`? → Update `templates/data-prepper-pipeline-secret.yaml` | ||
| 4. Did a Prometheus config change in `docker-compose/prometheus/prometheus.yml`? → Update the `prometheus:` section in `values.yaml` | ||
| 5. Did a Dashboards setting change in `docker-compose/opensearch-dashboards/opensearch_dashboards.template.yml`? → Update the `opensearch-dashboards.config` block in `values.yaml` | ||
| 6. Did a new service get added to `docker-compose.yml`? → May need a new template in `templates/` |
Member
There was a problem hiding this comment.
how do we keep this instruction list up to date when adding new services
Member
Author
There was a problem hiding this comment.
yes, may be I can add one line to discover new services
Signed-off-by: ps48 <pshenoy36@gmail.com>
lezzago
approved these changes
May 12, 2026
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.
Description
Resolves configuration drift between the Helm chart and Docker Compose deployments up through commit 367d855 (Dashboards icon side nav v2).
opensearchstagingrepo (3.7.0 is pre-release and not yet onopensearchproject); bumpChart.yamlappVersion to 3.7.0insecure_skip_verify: trueon theotlp/opensearchexporter andtelemetry.logs.level: infoopensearch.pingTimeout,opensearch_security.multitenancy.tenants.preferred,vis_type_vega.enableExternalUrls,server.compression.enabled,server.cors,csp.warnLegacyBrowsers,opensearchDashboards.enableIconSideNav, and theloggingblockextraFlags:web.enable-lifecycleandenable-feature=exemplar-storageservice/componentstatic labels to the otel-collector, opensearch, and data-prepper Prometheus scrape jobs for parity withdocker-compose/prometheus/prometheus.ymlcharts/observability-stack/SYNC.mddocumenting the last-synced Compose commit (367d855), what stays in sync vs. what is intentionally different, and a 6-step SOP for AI agents and contributors to detect and fix drift; README points to itCortex / Alertmanager / alerting from #226 (
85a64ca) is intentionally out of scope and will be synced in a separate follow-up PR. The SYNC.md checkpoint at367d855ensures the drift SOP will surface that work as still pending.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.