How kubernetes-sigs/karpenter works
Karpenter is Kubernetes cluster autoscaling software: it observes unschedulable workloads, evaluates placement constraints, provisions suitable nodes, and later removes unnecessary or out-of-date capacity. The graph covers the primary provisioning and node lifecycle, plus disruption, capacity buffers, dynamic resource allocation, overlays, and static NodePools. Controller wiring is sampled only in part; unsampled subsystem links are included only where the README or named runtime components support the capability, and uncertain call-level wiring is omitted.
Main entry points: provisioner.go Provisioner · cluster.go Cluster state · types.go Cloud provider · controller.go Node termination
Components 24
Provisioning
- Pod trigger
pkg/controllers/provisioning/controller.go - Provisioner
pkg/controllers/provisioning/provisioner.go - Constraint scheduler
pkg/controllers/provisioning/scheduling/scheduler.go - Scheduling rules
pkg/scheduling/requirements.go - NodeClaim and NodePool
pkg/apis/v1/nodeclaim.go - Cloud provider
pkg/cloudprovider/types.go - Device allocation
pkg/controllers/dynamicresources/deviceallocation/controller.go - Node overlays
pkg/controllers/nodeoverlay/controller.go
Node lifecycle
- NodeClaim lifecycle
pkg/controllers/nodeclaim/lifecycle/controller.go - Node termination
pkg/controllers/node/termination/controller.go - Drain and eviction
pkg/controllers/node/termination/terminator/terminator.go
Cluster state
- Cluster state
pkg/controllers/state/cluster.go - Resource informers
pkg/controllers/state/informer/pod.go - Virtual pod cache
pkg/state/virtualpods/virtualpods.go - Metrics controllers
pkg/controllers/metrics/node/controller.go
Capacity management
- Disruption controller
pkg/controllers/disruption/controller.go - Consolidation methods
pkg/controllers/disruption/consolidation.go - Static capacity
pkg/controllers/static/provisioning/controller.go - Static deprovisioning
pkg/controllers/static/deprovisioning/controller.go - Capacity buffers
pkg/controllers/capacitybuffer/controller.go
Other components
- Kubernetes API
- Workload Pods
- Provider infrastructure
- Kubernetes Nodes
Connections 29
- Workload Pods → Kubernetes API: submit workloads
- Kubernetes API → Pod trigger: enqueue provisionable pods
- Pod trigger → Provisioner: trigger provisioning
- Pod trigger → Cluster state: acknowledge pending pods
- Provisioner → Constraint scheduler: schedule workloads
- Constraint scheduler → Scheduling rules: evaluate constraints
- Provisioner → NodeClaim and NodePool: construct claims
- Provisioner → Cloud provider: request capacity
- Cloud provider → Provider infrastructure: create instances
- NodeClaim lifecycle → Cloud provider: launch claims
- NodeClaim lifecycle → Kubernetes API: patch claim status
- Provider infrastructure → Kubernetes Nodes: register nodes
- Kubernetes API → Resource informers: watch resources
- Resource informers → Cluster state: update state
- Disruption controller → Consolidation methods: evaluate candidates
- Disruption controller → Cluster state: inspect cluster
- Disruption controller → Provisioner: replace capacity
- Node termination → Drain and eviction: drain workloads
- Node termination → Cloud provider: delete instances
- Node termination → Kubernetes API: delete claims and nodes
- Static capacity → Kubernetes API: manage static capacity
- Static deprovisioning → Cluster state: select claims
- Static deprovisioning → Kubernetes API: delete claims
- Capacity buffers → Virtual pod cache: refresh virtual pods
- Capacity buffers → Provisioner: trigger provisioning
- Device allocation → Kubernetes API: track resource claims
- Node overlays → Kubernetes API: read and patch overlays
- Node overlays → Cluster state: invalidate consolidation state
- Metrics controllers → Cluster state: read node state