taskplaner/.planning/phases/07-gitops-foundation/07-CONTEXT.md

Phase 7: GitOps Foundation - Context

Gathered: 2026-02-03 Status: Ready for planning

## Phase Boundary

Register TaskPlanner with existing ArgoCD installation and verify GitOps workflow. ArgoCD server is already running and accessible — this phase applies the Application manifest and confirms auto-sync, self-heal, and deployment triggering work correctly.

## Implementation Decisions

Infrastructure State

• ArgoCD already installed and running in argocd namespace
• UI accessible at argocd.kube2.tricnet.de (TLS configured)
• Gitea repo credentials exist (gitea-repo secret) — same user can access TaskPlanner repo
• Application manifest exists at argocd/application.yaml with auto-sync and self-heal enabled

What This Phase Delivers

• Apply existing argocd/application.yaml to register TaskPlanner
• Verify Application shows "Synced" status in ArgoCD UI
• Verify auto-deploy: push to helm/taskplaner/values.yaml triggers deployment
• Verify self-heal: manual pod deletion restores to Git state

Repository Configuration

• Repo URL: https://git.kube2.tricnet.de/tho/taskplaner.git
• Use existing Gitea credentials (same user works for all repos)
• Internal cluster URL may be needed if external URL has issues

Claude's Discretion

• Whether to add repo credentials specifically for TaskPlanner or rely on existing
• Exact verification test approach
• Any cleanup of placeholder values in application.yaml (e.g., registry secret)

## Specific Ideas

• The argocd/application.yaml has a placeholder for registry secret that needs real credentials
• Sync policy already configured: automated prune + selfHeal
• No webhook setup needed for now — 3-minute polling is acceptable

## Deferred Ideas

None — discussion stayed within phase scope.

---

Phase: 07-gitops-foundation Context gathered: 2026-02-03