Skip to content

[mattermost-team-edition] add existingSecret for externalDB#467

Closed
berlincount wants to merge 1 commit intomattermost:masterfrom
berlincount:master
Closed

[mattermost-team-edition] add existingSecret for externalDB#467
berlincount wants to merge 1 commit intomattermost:masterfrom
berlincount:master

Conversation

@berlincount
Copy link
Copy Markdown

Summary

This change adds support for externally managed database secrets, allowing separate encryption or automatic rotation.

Ticket Link

Fixes #456
Fixes #392

Partially addresses #140

Related to #425, things are implemented differently in mattermost-enterprise-edition, I consider this approach more reliable.

@mattermost-build
Copy link
Copy Markdown
Contributor

Hello @berlincount,

Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

@mattermost-build
Copy link
Copy Markdown
Contributor

This PR has been automatically labelled "stale" because it hasn't had recent activity.
A core team member will check in on the status of the PR to help with questions.
Thank you for your contribution!

@serafdev
Copy link
Copy Markdown

Would love to see this feature merged, +1

@Ansible-man
Copy link
Copy Markdown

Why is this not getting merged?

@NeckBeardPrince
Copy link
Copy Markdown

Guys, this is really sad. I'm currently testing an Enterprise deployment of Mattermost and the lack of attention to this helm chart is really really putting me and my team off. Come on.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This pull request adds support for externally managed database secrets to the Mattermost Team Edition chart, allowing users to provide their own secrets for external databases.

  • Added configuration options for existing external secrets (existingSecret, existingSecretKey) in values.yaml and README.md.
  • Updated secret and deployment templates to conditionally use an external DB secret.
  • Bumped the chart version for release.

Reviewed Changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.

Show a summary per file
File Description
charts/mattermost-team-edition/values.yaml Added comments for new external DB secret configuration options.
charts/mattermost-team-edition/templates/secret-mattermost-dbsecret.yaml Conditional logic added for handling an externally provided secret.
charts/mattermost-team-edition/templates/deployment.yaml Updated environment variable secretKeyRef logic to support using an external secret.
charts/mattermost-team-edition/README.md Enhanced documentation with usage examples for externally managed secrets.
charts/mattermost-team-edition/Chart.yaml Incremented chart version from 6.6.60 to 6.6.61.
Comments suppressed due to low confidence (1)

charts/mattermost-team-edition/templates/secret-mattermost-dbsecret.yaml:16

  • [nitpick] The nested quotes in the tpl function may reduce readability and increase the risk of escaping issues. Consider using single quotes for the inner template or refactor the expression to improve clarity.
mattermost.dbsecret: {{ tpl "{{ .Values.externalDB.externalDriverType }}://{{ .Values.externalDB.externalConnectionString }}" . | b64enc }}

@berlincount berlincount closed this by deleting the head repository Mar 14, 2026
@Ansible-man
Copy link
Copy Markdown

@berlincount why was this closed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

mysql password should be able to reference Kubernetes secret Provide an option to pass the external database credentials, config etc through a secret

6 participants