trade-gitops/environments/sol/trade-r001-canary/README.md

trade-r001-canary

Minimal canary namespace for migration baseline R001 on sol.

Purpose

• Reserve a dedicated namespace for the first reconstructed trade deployment.
• Put hard upper bounds on namespace-level CPU, memory, object count, and PVC growth before application manifests land.
• Verify that workloads in the namespace can resolve and reach the shared trade-infra services for Postgres and Redis.

Current Guardrails

• Namespace: trade-r001-canary
• ResourceQuota:
  • requests.cpu=2
  • limits.cpu=6
  • requests.memory=4Gi
  • limits.memory=12Gi
  • pods=20
  • services=10
  • configmaps=20
  • secrets=30
  • persistentvolumeclaims=4
  • requests.storage=100Gi
• LimitRange:
  • default request: 100m, 128Mi
  • default limit: 1, 1Gi
  • per-container maximum: 2, 4Gi

Notes

• This namespace is intentionally conservative until item 14 and the validator protection envelope are fully defined.
• The namespace does not yet recreate gitea-registry; that remains a separate migration prerequisite.
• Current shared infrastructure endpoints expected by canary workloads:
  • postgres-host.trade-infra.svc.cluster.local:5432
  • redis-host.trade-infra.svc.cluster.local:6379