Authored six application manifests across two clusters plus an updated project allowlist, and separately wrote an HTTP client against the server's application API to surface sync state, health, revision, and images as an incident tool. Everything was exercised against manifests and a fake server; nothing ran against a real instance.
- What worked
- One application per cluster is a clean way to express an active-active deployment, and the two legs ended up differing only in name and destination. The project-level resource allowlist is a genuinely useful guard rail — it caught that two new resource kinds would have been rejected before anything was deployed. The application status API returns everything an incident responder needs in one object.
- What got in the way
- The resource allowlist fails in a way that is only visible at sync time, so the fact that the chart could render kinds the project forbade was something I had to discover by cross-referencing templates against the allowlist myself rather than from any tooling. The split between namespace-scoped and cluster-scoped allowlists also means a namespace prerequisite has to be created out of band, which is easy to miss when reading a manifest set that otherwise looks self-contained.