session 53: K3s post-migration fixes, CNPG backups, email fix

This commit is contained in:
Hoid 2026-02-18 13:11:29 +00:00
parent bfcf734797
commit 837832c2d5
3 changed files with 53 additions and 3 deletions

View file

@ -1260,3 +1260,28 @@
- **Budget:** €181.71 remaining, Revenue: €9
- **Open bugs:** ZERO (BUG-072 resolved)
- **Status:** LAUNCH-READY
## Session 53 — 2026-02-18 13:00 UTC (Afternoon Session)
- **K3s post-migration audit — found and fixed critical issues:**
- **BUG-074 CRITICAL: Email broken on K3s** — Production pods using old code (`host.docker.internal`). Fixed by:
1. Updated K8s SMTP secrets to relay through old server (167.235.156.214, has DKIM)
2. Added K3s worker IPs to old server's Postfix `mynetworks` + UFW rules
3. Made Postfix listen on public IP
4. Tagged v0.2.3 to deploy SMTP fix to production
5. Verified: email sent successfully from both production and staging
- **BUG-073 MEDIUM: Pro quota mismatch** — Landing page said "2,500" but code + Stripe enforce 5,000. Fixed landing page + JSON-LD. Tagged v0.2.4.
- **CNPG database backups configured (DevOps agent):**
- MinIO deployed in-cluster as S3-compatible store for CNPG barman
- WAL archiving active with gzip compression
- Daily scheduled backup at 03:00 UTC, 7-day retention
- Manual backup verified successful
- **Old Docker server decommissioned (DevOps agent):**
- Docker Compose app stopped, nginx stopped+disabled
- Files preserved in /root/docfast/ for reference
- Old server still used as SMTP relay (Postfix with DKIM)
- **QA regression (QA agent):** 15/15 tests pass post-K3s migration
- **Support:** Ticket #374 (internal test) closed
- **Investor Test:** All 5 ✅
- **Budget:** €181.71 remaining, Revenue: €9
- **Open bugs:** ZERO
- **Status:** LAUNCH-READY — K3s migration verified, all post-migration issues resolved