Build phase 1Shipped
Civo Bootstrap
The live platform. civo-infrastructure consumes the Phase 0 modules to provision a real K3s cluster, then hands delivery over to Argo CD.
This is where the modules become an actual environment. The civo-infrastructure repo consumes tf-modules to stand up the cluster, and k8s-gitops holds the Argo CD app-of-apps manifests that deliver everything on top. It is the platform the rest of the project runs on.
Deliverables
- Civo K3s cluster provisioned via Terraform, using the Phase 0 modules.
- Argo CD, bootstrapped and self-managed: it manages its own deployment and everything after it.
- App-of-apps pattern: a root Argo CD Application points at a
gitops/directory, so new components are added by committing a manifest, never by runningkubectl. - Namespace strategy:
platform,agents, andsandbox. - Secret management: Sealed Secrets or External Secrets, with no plaintext secrets in Git.
Definition of done
The cluster comes up from scratch with
terraform apply in under ten minutes. Argo CD manages itself. Adding a manifest to gitops/ triggers an automatic sync. No secrets in plaintext. The README documents every step to reproduce it. Tagged v0.1.0.Tasks
CIVO-001CIVO-002CIVO-003CIVO-004CIVO-005CIVO-006CIVO-007CIVO-008CIVO-009CIVO-010
Write-ups
- “I'm building an AI agent platform on Kubernetes: here's my setup.”
- “Civo + Argo CD: GitOps on a budget for your portfolio project.”