Add Slack Socket Mode worker deployment to the Helm chart - #35
Open
megative wants to merge 2 commits into
Open
Conversation
megative
force-pushed
the
feat/helm-slack-worker
branch
from
July 27, 2026 21:55
e6ee2f1 to
9e6ee38
Compare
Member
|
Hello, could you change branch to the release2.0. There is the changed |
The entrypoint has supported INCIDENTRELAY_SERVICE=slack since the
worker was introduced and docker-compose runs it, but the chart never
shipped a Deployment for it. As a result Slack interactive buttons
(Acknowledge and friends) were dead on Kubernetes: the web pod posted
messages, and nothing consumed the Socket Mode WebSocket.
Add deployment-slack.yaml mirroring the telegram worker, along with the
matching `slack` values block and a line in NOTES.txt.
Verified on a kind cluster: the pod reconciles channel config from the
database without a restart ("Slack Socket Mode connection started",
channel_count 1), and an alert delivered through a webhook route can be
acknowledged from Slack.
megative
force-pushed
the
feat/helm-slack-worker
branch
from
July 28, 2026 10:32
9e6ee38 to
692ac9d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
entrypoint.shhas supportedINCIDENTRELAY_SERVICE=slacksince the worker was added, anddocker/docker-compose.ymlruns it asincidentrelay-slack— but the Helm chart never shipped a Deployment for it. The chart even rendersconfig.logging.slack_worker_fileinto the config Secret, so the omission looks accidental.Effect on Kubernetes: Slack interactive buttons were dead. The web pod posts messages through
chat.postMessage, but nothing held the Socket Mode WebSocket, so Acknowledge and friends did nothing.Change
templates/deployment-slack.yaml— mirrors the telegram worker (single replica,Recreate, no migrations, shared config/data/logs volumes)values.yaml—slackblock, enabled by default liketelegram; harmless without a configured Slack app, the worker idlesNOTES.txt— slack line in the component listREADME.md— mention the workerVerification
Manually deployed on a kind cluster (k8s v1.36.1) from a locally built image:
1/1 Running, 0 restarts;/healthzand/readyzreturn 200 to kube-probe, also through the ServiceSlack Socket Mode connection started,channel_count: 1helm lintclean;--set slack.enabled=falseremoves the Deployment