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

feat: add proxyVarsFromSecret value #196

Closed
wants to merge 19 commits into from

Conversation

aslafy-z
Copy link
Contributor

@aslafy-z aslafy-z commented Apr 9, 2024

Replaces #141

@aslafy-z aslafy-z force-pushed the feat/proxyVarsFromSecret branch 3 times, most recently from 77997af to ad9329b Compare April 9, 2024 10:22
Signed-off-by: Zadkiel AHARONIAN <[email protected]>
@aslafy-z aslafy-z force-pushed the feat/proxyVarsFromSecret branch from ad9329b to a78c177 Compare April 9, 2024 10:23
@aslafy-z aslafy-z closed this Apr 9, 2024
@pierluigilenoci pierluigilenoci marked this pull request as ready for review April 9, 2024 11:11
@pierluigilenoci
Copy link
Contributor

@tuunit What do you think of this proposal?

envFrom:
- secretRef:
name: {{ . }}
{{- end }}
env:
{{- if .Values.proxyVarsAsSecrets }}
Copy link
Member

@tuunit tuunit Feb 7, 2025

Choose a reason for hiding this comment

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

proxyVarsAsSecrets and proxyVarsFromSecret should be mutually exclusive. Therefore I would like to see this check extended so that proxyVarsAsSecrets aren't rendered when proxyVarsFromSecret is set

Copy link
Contributor

Choose a reason for hiding this comment

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

This PR was given to us as a "gift"; if we want to bring it in, we must introduce the changes we want. 🤷🏻‍♂️

@tuunit tuunit force-pushed the feat/proxyVarsFromSecret branch from 06d61e5 to b7bab50 Compare February 10, 2025 19:18
@tuunit tuunit force-pushed the feat/proxyVarsFromSecret branch from b7bab50 to e2ae4b8 Compare February 10, 2025 19:20
@@ -237,7 +242,7 @@ spec:
{{- if .Values.extraEnv }}
{{ tpl (toYaml .Values.extraEnv) . | indent 8 }}
{{- end }}
{{- if .Values.envFrom }}
{{- if and (not .Values.envFromExistingSecret) .Values.envFrom }}
envFrom:
Copy link
Member

Choose a reason for hiding this comment

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

@pierluigilenoci I refactored the PR a little bit and gave the variable a better name but then I realised we already have an envFrom parameter that allows for using a secret as a source like so:

envFrom:
  - secretRef:
      name: my-secret

in the values.yaml without any changes to the chart.

Copy link
Member

Choose a reason for hiding this comment

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

Therefore I don't see the benefit of this addition to the helm chart 🤔

Copy link
Contributor

Choose a reason for hiding this comment

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

The original idea of PR has probably been lost over time.
However, you can find it in this comment:
#141 (comment)

Copy link
Member

Choose a reason for hiding this comment

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

Since then it has been replaced with a more generic solution:
#201

Copy link
Member

Choose a reason for hiding this comment

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

I would therefore close this PR.

@aslafy-z aslafy-z deleted the feat/proxyVarsFromSecret branch February 11, 2025 15:09
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.

3 participants