How csantanapr/terraform-eks-cilium works
Project Type and Purpose
• This is an “Infrastructure-as-Code” project using Terraform to provision AWS resources (VPC and EKS) and install Cilium with Prefix Delegation.
• The goal is to create a highly available EKS cluster, configure Cilium as the CNI, and enable each node to host >29 pods via AWS Prefix Delegation.
File Structure
• Top-level:
• 1_vpc/ – Terraform module to provision the VPC, subnets, route tables, IGW, NAT Gateway, etc.
• 2_eks/ – Terraform module to provision the EKS control plane, node groups, Helm values for Cilium (values_cilium.yaml), and bootstrap settings.
• values.yaml – global Helm overrides.
• Scripts & Config:
• max-pods-calculator.sh – helper to compute pod capacity per instance type.
• .gitignore – standard.
Gather Insights from README
• Shows sequence: “terraform apply” in 1_vpc, then in 2_eks with custom vars.
• Describes Cilium components (operator, daemonset, hubble, relay, UI).
• Verifies node allocatable pods > default.
• Uses AWS CLI, kubectl, Terraform CLI, and Cilium CLI.
– Developer Workstation (Terraform CLI, AWS CLI, kubectl, Cilium CLI)
– Terraform State & Modules (1_vpc, 2_eks)
– AWS VPC
• Public Subnets + Internet Gateway
• Private Subnets + NAT Gateway
• Route Tables
– EKS Control Plane (managed by AWS)
– EKS Worker Node Group(s)
– Cilium CNI
• cilium-operator (Deployment)
• cilium DaemonSet (data-plane)
• Hubble components (UI, Relay)
– Sample Application (100 nginx pods)
• Developer Workstation → Terraform → AWS VPC & EKS
• EKS Control Plane ↔ Worker Nodes (Kube API)
• Worker Nodes ↔ AWS Prefix Delegation APIs (to allocate /28 prefixes per node)
• Worker Nodes (Cilium agent) ↔ Cilium operator (control-plane)
• Cilium Data-Plane ↔ Pod networking (VXLAN, IPAM)
• kubectl / Cilium CLI → EKS Control Plane (commands & status checks)
c. Architectural Patterns & Design Principles:
• Infrastructure as Code (IaC) layered modules (VPC first, then EKS)
• Kubernetes control-plane separation from data-plane
• CNI offloading pod networking to AWS Prefix Delegation
• Declarative configuration via Helm values
d. Key Technologies / Frameworks:
• Terraform (modules, providers)
• AWS Services: VPC, EKS, EC2 (Node Groups), IAM, CloudWatch, etc.
• Kubernetes
• Cilium (operator, daemonset, Hubble)
• Helm (values.yaml, values_cilium.yaml)
• AWS CLI, kubectl, Cilium CLI
Diagramming Conventions
• IaC layer (Terraform) in blue
• AWS infra layer in orange
• Kubernetes layer in green
• CNI / Cilium layer in purple
• Rectangles for compute (EC2 nodes, pods)