How aws/karpenter works
Main Components (Core Architecture)
• Karpenter Controller (main orchestrator)
• NodeClaim Controller
• NodePool Controller
• NodeClass Controller
• Interruption Controller
• Kubernetes API Server
• AWS Services (EC2, IAM, SQS, SSM, Pricing API)
c. Resource Management (Right side):
• Instance Types Provider
• Launch Template Provider
• AMI Family Provider
• Security Group Provider
• Subnet Provider
Data Flow and Interactions
• Watch flows from Kubernetes API Server to Karpenter Controller
• Provisioning flows from Controller to AWS Services
• Event flows from AWS Services through SQS to Interruption Controller
• Configuration flows from NodePools/NodeClaims to the Controller
a. Node Provisioning Flow (Green):
• Unschedulable Pod Detection
• Constraint Evaluation
• Node Creation
• Node Registration
b. Node Deprovisioning Flow (Red):
• Empty Node Detection
• Consolidation Evaluation
• Node Termination
Integration Points
Connections to:
• CloudWatch Metrics
• Prometheus Metrics (via ServiceMonitor)
• Helm Controller
• AWS Cloud Provider
Component Details
• Component Name
• Key Responsibilities
• Dependencies
• Configuration Sources
Architectural Patterns
Highlight:
• Controller Pattern
• Provider Pattern
• Event-Driven Architecture
• Cloud Integration Pattern
Styling Guidelines:
• Infrastructure layer (bottom)
• Core services layer (middle)
• API/Interface layer (top)