Skip to content

fix(tempo-distributed): order of the registry and pullSecrets to be i…#4026

Open
JulienDelavande wants to merge 1 commit intografana:mainfrom
JulienDelavande:main
Open

fix(tempo-distributed): order of the registry and pullSecrets to be i…#4026
JulienDelavande wants to merge 1 commit intografana:mainfrom
JulienDelavande:main

Conversation

@JulienDelavande
Copy link
Copy Markdown

…njected

Description

Problem
The coalesce function in _helpers.tpl had an incorrect priority order for registry and pullSecrets values. The global values were taking precedence over more specific tempo and component values, preventing proper overrides.

Solution
Changed the priority order in the helper functions to follow a logical hierarchy from most specific to least specific:

  • component (highest priority) - Component-specific configuration (e.g., ingester, distributor)
  • tempo - Tempo-wide configuration
  • global (lowest priority) - Shared configuration across all charts

Changes

  • tempo.tempoImage: Updated $registry coalesce order from .global.registry → .component.registry → .tempo.registry to .component.registry → .tempo.registry → .global.registry
    tempo.imagePullSecrets: Updated $imagePullSecrets coalesce order from .global.pullSecrets → .component.pullSecrets → - .tempo.pullSecrets to .component.pullSecrets → .tempo.pullSecrets → .global.pullSecrets

Impact
This fix allows users to properly override global registry and pullSecrets settings at the tempo or component level, which is the expected behavior for Helm chart value inheritance.

@CLAassistant
Copy link
Copy Markdown

CLAassistant commented Nov 26, 2025

CLA assistant check
All committers have signed the CLA.

…njected

Signed-off-by: Julien Delavande <juliendelavande@gmail.com>
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.

2 participants