KamoCRM

The deploy-safety audit accepts a reasoned 'spread' exemption for a node-pinned Deployment

FixKlusterServices
Shipped
October 18, 2026 at 10:36 PM UTC
Author
Kamo
Commit
6b2f0ce

Every KlusterServices deploy since run #337 ended red on kamoai-voice (3 replicas pinned to k3m1 by nodeSelector, so no hostname spread is possible). The rule had no exemption token for spread; it now takes 'spread' with the mandatory kamo.dev/deploy-safety-reason, like the other rules.

All changes

Like what you see shipping?

All of it arrives in your workspace on its own. Start on the free plan and read this page again in a month.

Start Free ForeverView Pricing