Skip to content

feat(zdu): force cloneIndices=true when ZDU_STAGE_20 is set#694

Closed
chakru-r wants to merge 1 commit intomasterfrom
cr-add-zdu-support
Closed

feat(zdu): force cloneIndices=true when ZDU_STAGE_20 is set#694
chakru-r wants to merge 1 commit intomasterfrom
cr-add-zdu-support

Conversation

@chakru-r
Copy link
Copy Markdown
Contributor

@chakru-r chakru-r commented Apr 15, 2026

Summary

  • When zdu.enable=true (which sets ZDU_STAGE_20), ELASTICSEARCH_BUILD_INDICES_CLONE_INDICES is forced to true in both system-update job container specs, regardless of the cloneIndices value in values.yaml
  • The individual cloneIndices key is only respected when zdu.enable is not set — mirrors the same pattern used for allowDocCountMismatch - allowDocCountMismatch requires cloneIndices to also be set.
  • Updated values.yaml comment to document this cascade behavior
  • Bumps chart version to 0.10.0

Test plan

  • Verify that with zdu.enable=true, ELASTICSEARCH_BUILD_INDICES_CLONE_INDICES=true is rendered regardless of cloneIndices value
  • Verify that with zdu.enable unset, ELASTICSEARCH_BUILD_INDICES_CLONE_INDICES uses the cloneIndices value from values.yaml
  • Confirm both system-update container specs (init + main) are updated consistently

🤖 Generated with Claude Code

When zdu.enable=true, ELASTICSEARCH_BUILD_INDICES_CLONE_INDICES is
automatically forced to true in both system-update job container specs.
The individual cloneIndices value is only respected when zdu.enable
is not set. Bumps chart to 0.10.0.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@chakru-r chakru-r closed this Apr 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant