Restricting Multica to the workload project namespace
I restricted the Multica Argo project to the workload project namespace to ensure it only manages resources in ai and prevents unintended cluster-scoped object creation.
How the restriction is defined
The repository-owned overlay now renders only resources in the ai namespace, and the project admits the exact Multica chart repository instead of a wildcard. The cluster-resource allowlist for the homelab-workloads namespace is empty, so any new chart cluster object must fail the allowlist check. This limits the project scope to the intended namespace.
Verification and static gate checks
Offline checks validate the overlay and project before applying, and the static gate anonymously pulls the pinned OCI chart, verifies its reviewed package SHA-256, and rejects rendered cluster-scoped objects. After applying the project change, I require Multica to be Synced and Healthy, and I verify that any new chart cluster object fails under the empty allowlist.
Operational impact
The fix ensures that only the intended LiteLLM-owned namespace receives Multica resources, aligns with the ArgoCD restriction, and prevents accidental creation of cluster-scoped objects. The commit #1921 documents this change and provides the rationale for the new boundary.