Skip to content

Pod scheduling events

Pod scheduling events are specific log entries recorded in the Events section of a Pod's status that describe the steps taken by the Kubernetes Control Plane to assign the Pod to a specific Node.^[400-devops-06-kubernetes-k8s-learning-03pod-readme.md]

Common Events

The most frequent events encountered during this lifecycle phase involve the default-scheduler and the kubelet.

  • Scheduled: This event indicates that the scheduler has successfully found a suitable Node for the Pod and has assigned it to that node.^[400-devops-06-kubernetes-k8s-learning-03pod-readme.md]
  • Pulling: Once scheduled, the kubelet on the target node initiates the process of downloading the required container image from the registry.^[400-devops-06-kubernetes-k8s-learning-03pod-readme.md]
  • Pulled: This event confirms that the container image has been successfully retrieved.^[400-devops-06-kubernetes-k8s-learning-03pod-readme.md]
  • Created: After the image is available, the container is created.^[400-devops-06-kubernetes-k8s-learning-03pod-readme.md]
  • Started: This final event marks the successful start of the container process.^[400-devops-06-kubernetes-k8s-learning-03pod-readme.md]

Sources

^[400-devops-06-kubernetes-k8s-learning-03pod-readme.md]