How the0mikkel/hetzner-k3s works
Main Components
a) Infrastructure Layer:
• Hetzner Cloud Platform
• Network Infrastructure
• Node Groups (Control Plane and Worker Nodes)
b) Kubernetes Layer:
• k3s Distribution
• Core Components
• Storage System
c) Application Layer:
• ArgoCD (Continuous Delivery)
• Ingress Controller
• Monitoring (Prometheus)
• Database (PostgreSQL Operator)
• Certificate Management (cert-manager)
• Sample Applications (hello-world)
┌─────────────────────────────────────────┐
• Hetzner Cloud │
• ┘
┌─────────────────┐ ┌─────────────────┐
• Terraform │ │ hetzner-k3s │
• Approach │ │ Approach │
• ┘ └─────────────────┘
┌─────────────────────────────────────────┐
• k3s Cluster │
• ┌──────────┐ ┌──────────┐ ┌──────────┐ │
• ArgoCD │ │ Ingress │ │ Cert- │ │
• ┘ └──────────┘ │ Manager │ │
• ┌──────────┐ ┌──────────┐ └──────────┘ │
• Prometheus│ │PostgreSQL│ │
• ┘ └──────────┘ │
• ┘
🔷 Cloud Infrastructure
🔶 Management Tools
🔰 Kubernetes Components
🔮 Application Services
→ Direct Connection
⟢ Deployment Flow
Additional Details
• Version control integration (Git repository)
• Configuration management flow
• Backup and snapshot management (reference to hcloud-microos-snapshots.pkr.hcl)
• Network flow between components
• Security boundaries and access controls
Important Relationships to Highlight
• Terraform/hetzner-k3s → Hetzner Cloud API
• Infrastructure → k3s Cluster
• ArgoCD → Application Deployments
• Ingress → External Access
• Cert-Manager → TLS/Security
• Prometheus → Monitoring Flow