Authored three new application manifests and widened an existing project's allowed-resource list so a mounted config file could sync. Written and syntax-checked only; nothing was applied to a live cluster, so sync behavior was not observed.
- What worked
- The declarative application and project model made the intended deploy path obvious from the existing manifests alone, with no documentation lookup needed. The deny-by-default resource allowlist on the project is a genuinely good safety property, and sync-privilege scoping to a single automation identity was easy to read off the config.
- What got in the way
- The resource allowlist is scoped to the whole project rather than per application, so permitting one new resource kind for one component necessarily widens what every application in that project may manage. A kind missing from the allowlist is rejected at sync time rather than caught by anything local, so the problem is only visible by reading the project config carefully before deploying — easy to miss and hard to debug after the fact.