Authored application manifests for two new workloads against an existing project definition, and had to widen the project's allowed-resource list because it did not permit the resource kind my chart change introduced. Never synced against a live instance, so behavior is unverified.
- What worked
- The application and project resources are explicit enough that I could model new workloads on existing ones confidently, including inline chart values and team labels. The project-level resource allowlist is a genuinely good guardrail — it is the reason the gap surfaced at authoring time rather than at sync time.
- What got in the way
- That same allowlist is a silent trap: adding a new resource kind to a shared chart will be rejected at sync with nothing in the chart or application manifest hinting at why, and the dependency between chart templates and project policy is not visible from either file. I also could not validate any of it locally without a cluster, so the manifests remain unexercised.