Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[tempo-distributed] Adds global extraEnv support to deployed components #3333

Merged
merged 1 commit into from
Oct 3, 2024

Conversation

rbrady
Copy link
Contributor

@rbrady rbrady commented Sep 27, 2024

Most of the deployed components did not apply the global extraEnv in the deployment templates. This resulted in having to duplicate extraEnv vars in the values/overrides files. This change uses the pattern from mimir to create an env: for a deployment if the .Values.global.extraEnv or .Values..extraEnv exists. It also adds the global extraEnv section to the values.yaml file.

Closes #3332

@CLAassistant
Copy link

CLAassistant commented Sep 27, 2024

CLA assistant check
All committers have signed the CLA.

@rbrady rbrady changed the title Adds global extraEnv support to deployed components [tempo-distributed] Adds global extraEnv support to deployed components Sep 27, 2024
@rbrady rbrady force-pushed the rbrady/3332-apply-global-extraEnv branch from e0e60d6 to 32b098a Compare September 27, 2024 16:32
Copy link
Collaborator

@Sheikh-Abubaker Sheikh-Abubaker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @rbrady could you please share the mimir reference for this change.

@rbrady rbrady force-pushed the rbrady/3332-apply-global-extraEnv branch from 32b098a to 8257470 Compare September 27, 2024 17:59
Copy link
Collaborator

@Sheikh-Abubaker Sheikh-Abubaker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Thanks! for the Contribution @rbrady, keep them coming!

Copy link
Member

@mapno mapno left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Most of the deployed components did not apply the global extraEnv in the deployment templates.  This resulted in having to duplicate extraEnv vars
in the values/overrides files.  This change uses the pattern from mimir to create an env: for a deployment if the .Values.global.extraEnv or
.Values.<component>.extraEnv exists.  It also adds the global extraEnv section to the values.yaml file.

Signed-off-by: Ryan Brady <[email protected]>
@rbrady rbrady force-pushed the rbrady/3332-apply-global-extraEnv branch from 8257470 to 2126cb6 Compare October 3, 2024 17:49
@rbrady rbrady merged commit 350783e into main Oct 3, 2024
6 checks passed
@rbrady rbrady deleted the rbrady/3332-apply-global-extraEnv branch October 3, 2024 17:52
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.

Tempo deployed components do not apply global extraEnv
4 participants