fix(helm): template reindex ES cronjob SEARCH_HOST instead of hardcoding prod host [sc-44754] - #3397
Open
yodem wants to merge 1 commit into
Open
fix(helm): template reindex ES cronjob SEARCH_HOST instead of hardcoding prod host [sc-44754]#3397yodem wants to merge 1 commit into
yodem wants to merge 1 commit into
Conversation
…ing prod host [sc-44754] The reindex-elastic-search CronJob hardcoded the production ES hostname "elasticsearch-1b-es-http.elasticsearch.svc", which does not resolve in the dev cluster, so the job could not run in dev/cauldrons (e.g. sk-squad-feature). Template SEARCH_HOST from .Values.nginx.SEARCH_HOST, matching the sibling index-from-queue cronjob. prod/preprod override nginx.SEARCH_HOST to the prod host (unchanged behavior); dev/cauldrons inherit the working default elasticsearch-es-default.elasticsearch. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
📊 Code Quality Score: 1/100
Was this score accurate? 👍 Yes · 👎 No Scored by GitVelocity · How are scores calculated? |
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.
Problem
The
reindex-elastic-searchCronJob template hardcodes the production Elasticsearch hostname, so the job cannot run in the dev cluster / cauldrons.helm-chart/sefaria/templates/cronjob/reindex-elasticsearch.yaml:That name doesn't resolve in dev. ES is healthy there — the services that actually exist in the dev
elasticsearchnamespace are:Reported by Steve while trying to run a reindex job for the
sk-squad-featurecauldron (had tosedthe host to work around it).Root cause
This was the only cronjob template hardcoding
SEARCH_HOST. The siblingindex-from-queue.yamlalready templates it from.Values.nginx.SEARCH_HOST.Fix
Template
SEARCH_HOSTfrom.Values.nginx.SEARCH_HOST, matchingindex-from-queue.yaml.envs/prod/helmrelease.yaml) and preprod (build/ci/preprod-values.yaml) overridenginx.SEARCH_HOSTtoelasticsearch-1b-es-http.elasticsearch.svc→ behavior unchanged.elasticsearch-es-default.elasticsearch, which resolves in dev.Verified with
helm template:elasticsearch-es-default.elasticsearchelasticsearch-1b-es-http.elasticsearch.svcChart-level fix, not a per-cauldron patch.
Notes
cronJobs.reindexElasticSearch.SEARCH_HOST_ES6/ES8invalues.yamlare dead config (referenced nowhere) — left for a follow-up cleanup.Story: sc-44754
🤖 Generated with Claude Code