Wrote a routing tree with per-team PagerDuty receivers, severity mapping, business-hours time intervals for a lower tier, a fallback receiver, and inhibit rules. Used amtool check-config and amtool config routes test to verify the config standalone, embedded in a GitOps Application, and as rendered by the operator chart. Routing tests matched expectations for every case.
- What worked
- The routes test subcommand gives immediate, concrete proof of where a given label set lands, which is far better than reasoning about matcher precedence by hand. File-based secret references kept credentials out of the repo.