e15e60c810
CRITICAL: ArgoCD is installed but NOT configured yet Changes: - Expanded FASE 4 in ROADMAP.md with detailed ArgoCD setup steps - Added ArgoCD ApplicationSet configuration for preview environments - Created TODO-ARGOCD.md as explicit reminder file - Added comprehensive checklist for FASE 4 (won't forget!) ArgoCD details: - URL: https://argocd.fuq.tv - Status: Installed, pods running, NOT configured - When: FASE 4 (after Frontend + Agents are done) - Why: Critical for preview environments automation - Time: ~2-3 hours to configure fully TODO-ARGOCD.md will be deleted after completing FASE 4. Co-Authored-By: Claude Sonnet 4.5 (1M context) <noreply@anthropic.com>
167 lines
3.9 KiB
Markdown
167 lines
3.9 KiB
Markdown
# ⚠️ RECORDATORIO: ArgoCD está INSTALADO pero NO CONFIGURADO
|
|
|
|
**Estado**: ArgoCD instalado en el cluster, esperando configuración en FASE 4
|
|
**Fecha instalación**: 2026-01-19
|
|
**URL**: https://argocd.fuq.tv
|
|
**Credenciales**: admin / LyPF4Hy0wvp52IoU
|
|
|
|
---
|
|
|
|
## 🚨 NO OLVIDAR
|
|
|
|
Cuando llegues a **FASE 4** del ROADMAP, ArgoCD debe ser configurado **ANTES** de implementar preview environments.
|
|
|
|
---
|
|
|
|
## 📍 Estado actual
|
|
|
|
```
|
|
✅ ArgoCD pods corriendo en namespace argocd
|
|
✅ ArgoCD UI accesible en https://argocd.fuq.tv
|
|
✅ Ingress configurado con TLS
|
|
✅ Credenciales funcionando
|
|
❌ NO hay Applications configuradas
|
|
❌ NO está conectado a Gitea
|
|
❌ NO está deployando nada automáticamente
|
|
```
|
|
|
|
**Verificar estado**:
|
|
```bash
|
|
export KUBECONFIG=~/.kube/aiworker-config
|
|
kubectl get pods -n argocd
|
|
kubectl get applications -n argocd # Debe estar vacío
|
|
```
|
|
|
|
---
|
|
|
|
## ⏭️ Próximos pasos (FASE 4)
|
|
|
|
### 1. Quick Test (5 min)
|
|
```bash
|
|
# Verificar acceso
|
|
open https://argocd.fuq.tv
|
|
# Login: admin / LyPF4Hy0wvp52IoU
|
|
|
|
# Verificar que UI carga correctamente
|
|
# Debe mostrar: "No applications"
|
|
```
|
|
|
|
### 2. Conectar Gitea (10 min)
|
|
```bash
|
|
# Install ArgoCD CLI si no está
|
|
brew install argocd
|
|
|
|
# Login
|
|
argocd login argocd.fuq.tv --username admin --password LyPF4Hy0wvp52IoU
|
|
|
|
# Agregar repo de Gitea
|
|
argocd repo add https://git.fuq.tv/admin/aiworker.git \
|
|
--username admin \
|
|
--password 159a5de2a16d15f33e388b55b1276e431dbca3f3
|
|
```
|
|
|
|
### 3. Primera Application (10 min)
|
|
```bash
|
|
# Crear app para backend
|
|
argocd app create backend \
|
|
--repo https://git.fuq.tv/admin/aiworker.git \
|
|
--path k8s/backend \
|
|
--dest-server https://kubernetes.default.svc \
|
|
--dest-namespace control-plane \
|
|
--sync-policy automated
|
|
|
|
# Verificar en UI
|
|
open https://argocd.fuq.tv
|
|
# Debe aparecer "backend" app en estado "Synced"
|
|
```
|
|
|
|
### 4. Test GitOps Flow (5 min)
|
|
```bash
|
|
# Cambiar algo en k8s/backend/deployment.yaml
|
|
# Por ejemplo: replicas: 2 → replicas: 3
|
|
|
|
git add k8s/backend/deployment.yaml
|
|
git commit -m "Test ArgoCD auto-sync"
|
|
git push
|
|
|
|
# Esperar max 3 minutos
|
|
# ArgoCD debe detectar cambio y auto-deployar
|
|
|
|
# Verificar
|
|
kubectl get deployment backend -n control-plane
|
|
# Debe mostrar 3 replicas
|
|
```
|
|
|
|
---
|
|
|
|
## 🎯 Por qué es importante NO olvidarlo
|
|
|
|
### Sin ArgoCD (estado actual):
|
|
```
|
|
Manual kubectl apply después de cada build
|
|
↓
|
|
Propenso a errores
|
|
↓
|
|
Sin audit trail
|
|
↓
|
|
Rollback complicado
|
|
```
|
|
|
|
### Con ArgoCD (FASE 4):
|
|
```
|
|
Git push → ArgoCD auto-sync
|
|
↓
|
|
Git es source of truth
|
|
↓
|
|
Rollback = git revert
|
|
↓
|
|
UI visual del cluster
|
|
↓
|
|
Preview environments automáticos ✨
|
|
```
|
|
|
|
---
|
|
|
|
## 📊 Beneficios específicos para AiWorker
|
|
|
|
1. **Preview Environments**: ApplicationSets crean/destruyen namespaces automáticamente
|
|
2. **Multi-tenant**: Cada task = namespace aislado via ArgoCD
|
|
3. **Audit Trail**: Todo cambio queda en Git (compliance)
|
|
4. **Rollback**: `git revert` en lugar de `kubectl rollout undo`
|
|
5. **Drift Detection**: ArgoCD detecta si alguien hace kubectl directo
|
|
6. **Self-Healing**: Si pod muere, ArgoCD lo recrea desde Git
|
|
|
|
---
|
|
|
|
## 📚 Referencias
|
|
|
|
**Documentación completa**: `docs/06-deployment/gitops.md`
|
|
**ROADMAP FASE 4**: Línea 244-404 en `ROADMAP.md`
|
|
**ArgoCD Docs**: https://argo-cd.readthedocs.io/
|
|
|
|
---
|
|
|
|
## ✅ Checklist rápida para FASE 4
|
|
|
|
Cuando estés listo para FASE 4, usar esta checklist:
|
|
|
|
- [ ] Verificar ArgoCD accesible (https://argocd.fuq.tv)
|
|
- [ ] Login con credenciales (admin/LyPF4Hy0wvp52IoU)
|
|
- [ ] Instalar ArgoCD CLI (`brew install argocd`)
|
|
- [ ] Conectar repo de Gitea
|
|
- [ ] Crear Application para backend
|
|
- [ ] Crear Application para frontend
|
|
- [ ] Habilitar auto-sync
|
|
- [ ] Test: cambiar manifest → verificar auto-deploy
|
|
- [ ] Crear ApplicationSet para previews
|
|
- [ ] Integrar con backend API
|
|
- [ ] Configurar staging/production
|
|
|
|
**Tiempo estimado FASE 4**: 2-3 horas
|
|
|
|
---
|
|
|
|
**🔔 Este archivo existe para recordarte que ArgoCD está listo para usarse en FASE 4**
|
|
|
|
**Eliminar este archivo después de completar FASE 4**
|