Menu

Kubernetes CI Needs a Failure Budget for Email Jobs
📰

Kubernetes CI Needs a Failure Budget for Email Jobs

DEV Community: cicd·jasonmills94·9 days ago
#56J32D6q
#devtocicd#devto#dev#email#message
Reading 0:00
15s threshold

Email checks in CI are usually treated as a small assertion: send a message, wait for it, verify a link, then delete the test data. In a Kubernetes pipeline, that small assertion crosses several systems at once: a runner, a pod, a mail API, a queue, and often an external inbox.

When the check flakes, teams tend to add another retry. That makes the pipeline look calmer, but it also hides whether the application, the mail provider, or the test infrastructure is failing. A better pattern is to give email jobs an explicit failure budget and make every retry observable.

Why email jobs need their own failure budget

A failure budget is not permission to ignore broken delivery. It is a limit on tolerated uncertainty for one job. For example, a staging email check might allow one retry inside a five-minute deadline, but it should still fail if the message never arrives or if the same event is delivered twice.

This distinction matters for disposable test data.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.