Missing environment values for microservices deployment
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
Research direction
Read templates/chat-deployment.yaml around the referenced block at line 124 and compare it with the microservices prerequisites documentation. Render or inspect the chart with default values to verify that DISABLE_DB_WATCH, DISABLE_PRESENCE_MONITOR, and INTERNAL_SERVICES_ONLY are present alongside TRANSPORTER in the deployment environment; done means all four values are supplied as expected.
Written by the indexing model from the issue text.
Description
According to the documentation,microservices deployment should have the following environment values :
| Variable | Value | Description |
|---|---|---|
TRANSPORTER |
nats://nats:4222 |
NATS address |
DISABLE_DB_WATCH |
true |
Disables internal DB watcher and rely on mongodb-stream-hub |
DISABLE_PRESENCE_MONITOR |
true |
Disables presence monitoring and rely on the presence-service |
INTERNAL_SERVICES_ONLY |
true |
Do not run external services on rocket.chat process |
However, only TRANSPORTER is added in the following block, thus requiring to manually set environment variables in values :
extraEnv:
DISABLE_DB_WATCH: true
DISABLE_PRESENCE_MONITOR: true
INTERNAL_SERVICES_ONLY: true
Could these three be added to the same block ?
- 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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from RocketChat/helm-charts
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
RocketChat/helm-charts#237 · 1 reaction ·
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
RocketChat/helm-charts#166 ·
-
Wrong tag 5.4.1Open
Difficulty 1/5 Under an hour Newbie friendliness 62/100
RocketChat/helm-charts#84 · 1 comment ·
-
rocketchat: microservice, Synapse and well-known Deployments don't use the chart's ServiceAccountPossibly taken @martin-mat claimed this 27 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
RocketChat/helm-charts#242 ·
-
(feature request) add pipeline trigger, when rocketchat code is updated, to trigger a new 'dev' helm chart to be releasedMay be free again @devadharshini-162 claimed this 305 days ago, and no pull request is open. Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
RocketChat/helm-charts#218 · 2 comments ·
All issues in RocketChat/helm-charts
Similar issues
-
area: shell difficulty: easy enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
decision
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
btclib-org/claude-process#509 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
humblemuzzu/dumbtv#206 ·
Maintainers usually reply within 2 days