-
-
Notifications
You must be signed in to change notification settings - Fork 254
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
helm: add the posibility to add external secrets as env variables #465
base: main
Are you sure you want to change the base?
Changes from all commits
ebfb722
0f8a051
75c4f19
9416ffb
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -139,6 +139,26 @@ zulip: | |
SETTING_EMAIL_USE_SSL: "False" | ||
SETTING_EMAIL_USE_TLS: "True" | ||
ZULIP_AUTH_BACKENDS: "EmailAuthBackend" | ||
# -- Mount environment variables from secrets. Use the secret name. | ||
# If you have a secret with env. variables created named zulip-secrets | ||
# you will add: | ||
# ``` | ||
# envSecrets: | ||
# - zulip-secrets | ||
# - other-secrets | ||
# The secrets file you manually create in the namespace, can look something | ||
# like this (secrets need to be base64 encoded): | ||
# --- | ||
# apiVersion: v1 | ||
# kind: Secret | ||
# metadata: | ||
# name: zulip-secrets | ||
# type: Opaque | ||
# data: | ||
# SECRETS_email_password: MTIzNDU2Nzg5 | ||
# SECRET: Zm9vaXNiYXI= | ||
envSecrets: | ||
[] | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is it useful/necessary to have the There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. You mean the newline? There is a mix of practice of this. This: envSecrets:
[] And this: envSecrets: [] Have the same meaning, but I like the first one better - because it also indicates that the values that it is entered should be on a new line: envSecrets:
- secret_ONE: ERTY
- secret_TWO: YTRE So I think it helps the user. But as there are mix of standards in the helm chart, like: podSecurityContext:
{} And podAnnotations: {} There should be maybe a consensus around what should be used. I like the newline myself, as I think it helps to guide the user. |
||
# -- If `persistence.existingClaim` is not set, a PVC is generated with these | ||
# specifications. | ||
persistence: | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What does the
SECRET
one do -- is the point that it's not passed intozulip-secrets
, or is it? I feel like the documentation needs to be clearer about how to interpret this example.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agree, I will add better example.