Flipkart Marketplace Platform · View 20 of 25 · 6 · Operations
Decisions
- GitOps: Argo CD reconciles the cluster to Git, so the repository is the only way in and the audit trail is free
- Only signed images with an SBOM deploy; the policy engine rejects anything else at admission
- Progressive delivery with automatic rollback on an SLO burn-rate breach, so a bad release does not need a human to notice it
Environments
- Ephemeral per-PR environments for dev; a permanent staging with production-shaped, masked data
- A performance environment that replays production traffic at 10x before every sale event
- A code freeze window during sale events, enforced by policy — only flag flips and rollbacks are permitted
Risks
- Database migrations are the one change class GitOps does not make safe; expand-and-contract is mandatory and reviewed by hand
- Feature flags accumulate: an unreviewed flag is an untested branch in production
- The freeze window shifts risk rather than removing it — the release immediately after a sale is the riskiest of the quarter