Skip to content

Allow existing Secrets to be used for secret values (#18139)#18179

Closed
tedtramonte wants to merge 1 commit intomastodon:mainfrom
tedtramonte:main
Closed

Allow existing Secrets to be used for secret values (#18139)#18179
tedtramonte wants to merge 1 commit intomastodon:mainfrom
tedtramonte:main

Conversation

@tedtramonte
Copy link
Copy Markdown
Contributor

@tedtramonte tedtramonte commented Apr 29, 2022

This PR adds some functions to _helpers.tpl to facilitate using the correct Secret names throughout the chart's templates. It also adds some comments to the values.yaml file indicating how to use the existingSecret fields.

Closes #18139

@tedtramonte
Copy link
Copy Markdown
Contributor Author

tedtramonte commented Apr 29, 2022

@dunn So, as of this comment I think I have all the Secrets handled. While working through this, however, I noticed some values that should probably be considered sensitive are part of a ConfigMap. For example, mastodon.smtp.password, and several values in the various externalAuth sections.

They're not personally blocking me from running Mastodon, so if you'd rather leave those how they are to avoid breaking changes, that's fine with me. On the other hand, if you want them changed as part of this PR, I can probably make that happen too.

Let me know one way or the other and I'll clean this up and mark it ready for review.

@tedtramonte tedtramonte marked this pull request as ready for review May 2, 2022 16:57
@tedtramonte
Copy link
Copy Markdown
Contributor Author

Went ahead with avoiding any breaking changes for now and marked this ready for review.

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.

Use an existing Secret in Helm Chart

1 participant