Conversation
deployment-queue.yaml already includes api.commonAppEnvVars defined in charts/api/templates/_helpers.tpl. That helper emits ELASTICSEARCH_HOST when app.elasticSearchHost is configured, so the additional inline entry rendered the same environment variable twice. During local-dev testing, changing the Elasticsearch hostname through a Helm upgrade left one duplicate entry with the previous hostname. Kubernetes strategic merge patches identify environment entries by name, so duplicate names make updates ambiguous and can leave stale values in the pod specification. Remove the inline entry and retain the shared helper as the single source of ELASTICSEARCH_HOST. When the host is configured, the rendered queue deployment now contains exactly one entry with the configured value. **API chart `0.36.0` introduced the duplicate**, in commit `89fbef2`
addshore
force-pushed
the
fix/api-queue-elasticsearch-env
branch
from
September 27, 2026 22:52
d7ee613 to
8ce03a2
Compare
This branch has not been deployed
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
1 participant
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.
deployment-queue.yaml already includes api.commonAppEnvVars defined in charts/api/templates/_helpers.tpl.
That helper emits ELASTICSEARCH_HOST when app.elasticSearchHost is configured, so the additional inline entry rendered the same environment variable twice.
During local-dev testing, changing the Elasticsearch hostname through a Helm upgrade left one duplicate entry with the previous hostname. Kubernetes strategic merge patches identify environment entries by name, so duplicate names make updates ambiguous and can leave stale values in the pod specification.
Remove the inline entry and retain the shared helper as the single source of ELASTICSEARCH_HOST. When the host is configured, the rendered queue deployment now contains exactly one entry with the configured value.