From Pod Pending to Node Provisioning

From Pod Pending to Node Provisioning A workflow diagram generated by Archify. 01 / Trigger 02 / Auto Mode Controller 03 / Provisioning 04 / Scheduling Pod created · scheduling request · Trigger Pod created scheduling request Schedulable? · existing capacity? · Trigger Schedulable? existing capacity? Existing node · placed, no new node · Trigger Existing node placed, no new node Pending detected · Pod Pending state · Auto Mode Controller Pending detected Pod Pending state Check NodePool · analyze requirements · Auto Mode Controller Check NodePool analyze requirements Select instance · optimal instance type · Auto Mode Controller Select instance optimal instance type Provision node · start EC2 instance · Provisioning Provision node start EC2 instance Node bootstrap · kubelet registration · Provisioning Node bootstrap kubelet registration Node Ready · joined the cluster · Provisioning Node Ready joined the cluster Pod scheduling · Pod Running · Scheduling Pod scheduling Pod Running No Yes Legend Pod state Auto Mode Controller Scheduling decision EC2 node

Typical provisioning timeline

  • • EC2 instance start: 10-30 s
  • • AMI boot: 20-40 s
  • • kubelet registration: 5-10 s
  • • Pod scheduling: 1-5 s (40-90 s total)