Adding database authentication via existingSecret

Open
#201 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
helm, kubernetes, mongodb
Domain
database, devops

Research direction

Start at rocketchat/templates/secret.yaml:25,16 and trace how the MongoDB password is required during installation. Compare this handling with the Bitnami MongoDB chart's existingSecrets functionality. Done means the chart can use an existing secret without requiring mongodb.password or producing the reported passwords-array error.

Written by the indexing model from the issue text.

Description

Hello,

The current helm chart enforces a mongodb.password field. Where this field is not filled in you will get an error like such:

  • Error: INSTALLATION FAILED: execution error at (rocketchat/templates/secret.yaml:25:16): passwords array must have at least one entry

The issue with this is that this chart does not correctly inherit the settings or enable the existingSecrets functionality that the original mongodb bitnami chart does, because it will result in a panic if the password field is missing.

Dominant language
Shell
Stars
48
Forks
83
Avg merge
2m
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from RocketChat/helm-charts

All issues in RocketChat/helm-charts

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.