When does the Kubernetes Kube-Scheduler determine the node placement for a pod?

When does the Kubernetes Kube-Scheduler determine the node placement for a pod?

• A. After the pod has been created and registered in ETCD
• B. Before the pod is created
• C. After the cluster has been fully provisioned
• D. During pod deletion

Answer: (A)

Scheduling happens after you create the pod. The Pod is stored in etcd via the API server, and the scheduler watches for pods that have no node assigned yet (Pending). It then chooses a suitable node based on resources and constraints and binds the Pod to that node by setting the pod’s nodeName (or creating a Binding). Only after this binding does the Pod actually run on the selected node. So the node placement is determined after creation and registration in etcd, not before creation, during cluster provisioning, or during deletion.

Scheduling happens after you create the pod. The Pod is stored in etcd via the API server, and the scheduler watches for pods that have no node assigned yet (Pending). It then chooses a suitable node based on resources and constraints and binds the Pod to that node by setting the pod’s nodeName (or creating a Binding). Only after this binding does the Pod actually run on the selected node. So the node placement is determined after creation and registration in etcd, not before creation, during cluster provisioning, or during deletion.