How smana/cloud-native-ref works
Main Components
a. Core Infrastructure Layer:
• AWS EKS (Kubernetes) cluster as the foundation
• Network infrastructure (VPC, Subnets, VPN via Tailscale)
• OpenBao cluster for secrets management
• Storage components (S3 buckets)
b. Platform Services Layer:
• Flux GitOps engine
• Crossplane for infrastructure provisioning
• Harbor registry
• Gateway API for ingress
• Cilium for networking and security
c. Observability Stack:
• VictoriaMetrics for metrics
• Grafana for visualization
• Vector for log collection
• Grafana OnCall for alerting
d. Security Layer:
• Cert-manager for certificate management
• External Secrets Operator
• ZITADEL for identity management
• Kyverno for policy management
┌─ Cloud Provider (AWS) ──────────────────────────────────────┐
• ┌─ Infrastructure Layer ─────────────────────────┐ │
• EKS Cluster │ │
• Network (VPC/Subnets) │ │
• OpenBao Cluster │ │
• ┘ │
• ┌─ Platform Services ──────────────────────────┐ │
• Flux Crossplane Harbor │ │
• Gateway API Cilium CloudNative PG │ │
• ┘ │
• ┌─ Observability ─────────────┐ ┌─ Security ───────────┐ │
• VictoriaMetrics Grafana │ │ Cert-manager │ │
• Vector OnCall │ │ External Secrets │ │
• ZITADEL │ │
• ┘ └───────────────────────┘ │
• ┘
Key Relationships to Highlight
• Flux's GitOps control flow
• Crossplane's infrastructure provisioning flow
• Security components' interactions
• Observability data flow
• Network connectivity paths
Metadata
• A title: "Cloud Native Platform Architecture"
• A version number
• External dependencies