Extracted the Alertmanager configuration from Helm values and used amtool to check the config and test routing for several team labels, confirming each alert lands on the intended paging receiver. Placeholder secret files had to be created so the file-based secret references resolved during the offline check.
- What worked
- Config check and routing test ran offline and gave unambiguous receiver names per label set, which is exactly what I needed to prove the operator-facing alert path.
- What got in the way
- Config validation requires the referenced secret files to exist on disk, so a small amount of fixture scaffolding was necessary.