⚓ GitOps Infrastructure: ArgoCD & K3s

🏗 Project Architecture

This repository serves as the Single Source of Truth (SSOT) for my lightweight Kubernetes cluster infrastructure. Hosted on a Virtual Private Server (VPS) running K3s, it strictly adheres to GitOps principles using ArgoCD, ensuring that the cluster state always matches the declarative configurations stored in this repository.

🔗 Open the scheme in the Lucidchart

🧳 The App-of-Apps Pattern

To maintain scalability and clean logical separation, this repository implements the ArgoCD App-of-Apps pattern.

Instead of deploying individual manifests manually, a single root.yaml application is deployed, which recursively discovers and synchronizes all other applications defined in the apps/ directory.

📂 Repository Structure

.
├── apps/               # ArgoCD Application Wrappers
│   ├── monitoring.yaml # Kube-Prometheus-Stack definition
│   ├── portfolio.yaml  # Portfolio app definition
│   └── tikceto.yaml    # Tikceto microservices definition
├── bootstrap/          # Cluster Initialization
│   └── root.yaml       # The "App of Apps" entry point
└── manifests/          # Raw Kubernetes Resources
    ├── portfolio/      # Deployment, Ingress, Service
    └── tikceto/        # Backend, Frontend, Minio, Postgres, Ingress

⚙️ Cluster Bootstrapping

To deploy this entire infrastructure to a fresh Kubernetes cluster (assuming ArgoCD is pre-installed):

1. Apply the Root Application:

kubectl apply -f bootstrap/root.yaml

2. Automated Synchronization:

ArgoCD will detect the root application, which will subsequently deploy monitoring, portfolio, and tikceto. All dependencies, persistent volume claims, and ingresses will be provisioned automatically based on the sync policies.

📅 Backlog

• Add external secret manager
• Add the ELK Stack

---

Made with ❤️ by Yurii Yevtushenko