Slack log forwarder duplicate messages by replica count #7

New Issue

2026-06-12T19:38:15Z

rasmus commented

2026-06-12 19:38:15 +00:00

Each replica listens for doorlog changes in database and forwards changes to Slack. This is IMO the most sensible way, vs duplicating each statement, and calling out to Slack in multiple codebases (leading to 'where exactly did this originate from / is broken at?).

Reduced replicas to 1 for time being. Locking via built-in kube primitives seems sensible (as the service already talks to kube api).

Each replica listens for doorlog changes in database and forwards changes to Slack. This is IMO the most sensible way, vs duplicating each statement, and calling out to Slack in multiple codebases (leading to 'where exactly did this originate from / is broken at?). Reduced replicas to 1 for time being. Locking via built-in kube primitives seems sensible (as the service already talks to kube api).

rasmus referenced this issue from a commit

2026-06-12 19:39:12 +00:00

doorboy-proxy replicas to 1

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: k-space/doorboy-proxy#7