How stacksimplify/aws-eks-kubernetes-masterclass works
Main System Components
• AWS Infrastructure Layer:
– AWS EKS Cluster: The heart of the project where all containerized applications run.
– AWS Compute Resources: Both EC2-based nodes and Fargate-managed workloads.
– AWS Storage Components: EBS (via the CSI driver), plus integration with RDS for MySQL.
– AWS Load Balancing: Inclusion of Classic Load Balancer (CLB), Network Load Balancer (NLB), and Application Load Balancer (ALB) (with variations like Ingress SSL, context-based routing, ExternalDNS, etc.).
– AWS Container Registry: ECR in addition to pulling images from Docker Hub.
– AWS Developer Tools: CodeCommit, CodeBuild, and CodePipeline.
– Monitoring and Tracing: CloudWatch (Container Insights) and AWS X-Ray.
• Kubernetes & Microservices Layer:
– Foundational Kubernetes components: Pods, ReplicaSets, Deployments, Services (NodePort, ClusterIP, ExternalName) and Ingress.
– Specialized modules for Kubernetes concepts: Secrets, ConfigMaps, Liveness/Readiness Probes, Init Containers, Namespaces (with Limit Ranges and Resource Quota), and Storage (storage classes, PVCs, PVs).
– Actual Application Deployments: Microservices (for user management and notification services) and sample Nginx apps.
– Autoscaling: Horizontal Pod Autoscaler (HPA), Vertical Pod Autoscaler (VPA), and Cluster Autoscaler.
– Advanced Deployment Strategies: Canary deployments and distributed tracing with AWS X-Ray.
• Docker/CI-CD Layer:
– Docker images and containerization fundamentals.
– Build and push process from local Docker builds to AWS ECR.
– DevOps inclusive module using AWS developer tools for continuous integration and delivery.
Relationships & Interactions
• How the AWS CLI/eksctl creates and manages the EKS cluster.
• Deployment flow within the EKS cluster – from container images (Docker/ECR) being deployed as pods (with appropriate Kubernetes manifests) to how services are exposed via load balancers (CLB, NLB, ALB).
• Storage components: link the Kubernetes persistent volume claims (both for EBS and RDS external names) with the actual underlying AWS storage.
• Monitoring and tracing elements that capture logs and metrics and forward them to CloudWatch and AWS X-Ray.
Important Architectural Patterns & Principles
• Separation of Concerns: Group modules by functionality – cluster provisioning, containerization, Kubernetes fundamentals, load balancing, stateful services, autoscaling, CI/CD, and monitoring.
• Cloud-Native Design: Emphasize the loosely-coupled microservices architecture, container orchestration, and usage of managed AWS services.
Technologies, Frameworks & Libraries Involved
• AWS Services (EKS, EBS, RDS, ALB/NLB/CLB, ECR, CodeCommit/CodeBuild/CodePipeline, CloudWatch, X-Ray)
• Kubernetes (deployments, services, ingress, autoscaling, persistent volume concepts)
• Docker for containerization
• CI/CD tooling around AWS Developer Tools
Provide Concrete Elements for the Principal Software Engineer
• Containers inside the cluster representing various microservices (e.g., Notification Microservice, User Management Microservice, Nginx Apps) with respective Kubernetes objects (Pods, Deployments).
• Various Load Balancer components (for CLB, NLB, ALB) attached to Services/Ingress routes.
• Monitoring and Logging components feeding into CloudWatch Container Insights and AWS X-Ray for distributed tracing.