[Phase 3] Create deployment manifests (04-06) with MPP configurations

[jeremyeder]

Epic: #1, Phase: 3, Dependencies: #7 #8, Estimate: 4h. Create backend/frontend/operator deployment YAMLs with SINGLE_NAMESPACE_MODE and STORAGE_CLASS env vars.

[jeremyeder]

@claude go

[claude]

Claude finished @jeremyeder's task —— View job • claude/issue-9-20251002-2007 • Create PR ➔

---

Completed deployment manifests ✅

Tasks

• Gather context and understand project structure
• Review existing manifests for structure and naming
• Create 04-backend deployment manifest with MPP configs
• Create 05-frontend deployment manifest with MPP configs
• Create 06-operator deployment manifest with MPP configs
• Update kustomization.yaml to use new numbered files
• Commit and push changes
• Provide PR creation link

Summary

Created three deployment manifests (04-06) with Multi-Project Platform (MPP) configuration support:

04-backend-deployment.yaml

• Added SINGLE_NAMESPACE_MODE env var (default: false)
• Added STORAGE_CLASS env var (default: gp3-csi)
• Controls whether backend creates resources in single or multi-namespace mode

05-frontend-deployment.yaml

• Added SINGLE_NAMESPACE_MODE env var (default: false)
• Added STORAGE_CLASS env var (default: gp3-csi)
• Controls UI behavior for displaying resources across namespaces

06-operator-deployment.yaml

• Added SINGLE_NAMESPACE_MODE env var (default: false)
• Added STORAGE_CLASS env var (default: gp3-csi)
• Controls operator namespace creation and PVC provisioning behavior

kustomization.yaml

• Updated to reference numbered files: 01-namespace.yaml, 02-crds.yaml, 03-rbac.yaml, 04-backend-deployment.yaml, 05-frontend-deployment.yaml, 06-operator-deployment.yaml

The MPP configuration allows the platform to operate in either:

• Single-namespace mode (SINGLE_NAMESPACE_MODE=true): All resources created in operator's namespace
• Multi-namespace mode (SINGLE_NAMESPACE_MODE=false): Each project gets its own namespace

---

Job Run • Branch