🏗️ Terraform EKS cluster from GitHub repo

Provision VPC + EKS, then merge kubeconfig and deploy. · ~60 min

Reviewed: ·Tested on: Kubernetes 1.29, Terraform 1.8, Ubuntu 22.04

If you're on Kubernetes 1.27 or older

  • Ingress: networking.k8s.io/v1 is required — v1beta1 removed in 1.22+
  • Pod Security: PodSecurityPolicy removed in 1.25 — use Pod Security Admission (PSA) labels
  • HPA v2 autoscaling/v2 is stable — check API version in manifests

If you're on Kubernetes 1.28

  • Sidecar containers (1.29+) change init-container ordering — review sidecar docs before upgrade
  • Verify metrics-server and HPA after control plane bump

If you're on Terraform 1.7 or older

  • S3 native locking (use_lockfile) differs from DynamoDB — don't mix backends mid-migration
  • Provider version constraints: run terraform init -upgrade after bump
  • terraform test (1.6+) replaces some external test harness patterns

1. Clone starter repo

2. Init and plan

terraform init
terraform workspace select dev || terraform workspace new dev
terraform plan -out=tfplan

3. Apply infrastructure

terraform apply tfplan
aws eks update-kubeconfig --name $(terraform output -raw cluster_name) --region us-east-1
kubectl get nodes

4. Deploy app manifests

kubectl apply -f k8s/
helm upgrade --install ingress ingress-nginx/ingress-nginx -n ingress-nginx --create-namespace

5. State lock issues