How kea-chunsam/playus-terraform works
Project type and purpose
• This is an “Infrastructure-as-Code” Terraform repository.
• Its goal is to stand up a secure, multi-tier network on Kakao Cloud for the PlayUs application, hosting static React assets and a Spring API on Kubernetes behind an ALB.
File structure
• Top-level .tf files:
• network.tf defines the VPC, subnets (public vs. private)
• alb.tf defines the Application Load Balancer and its listeners/rules
• instance.tf and security.tf spin up bastion, NAT, web and K8s nodes plus security groups
• main.tf / data.tf / outputs.tf / variables.tf / require.tf glue modules together, import data sources, and export endpoints
• templates/ houses the user-data scripts (init-*.sh) used to bootstrap each instance role (bastion, NAT, web, K8s master/worker).
• terraform.tfvars.example shows required variables (credentials, sizes, CIDRs).
README for architectural insights
• Public Subnet: Bastion (SSH & Nginx Proxy Manager), NAT instance, ALB
• Private Subnet: React Web Server, Kubernetes Cluster (1 master + 2 workers)
• ALB port 80 routes “/” → Web server; “/api/*” → Kong ingress on K8s
• Security groups lock each component to only necessary ports