Topic 1 Question 94

Associate Cloud Engineer

Topic 1 Question 94
You create a Deployment with 2 replicas in a Google Kubernetes Engine cluster that has a single preemptible node pool. After a few minutes, you use kubectl to examine the status of your Pod and observe that one of them is still in Pending status: What is the most likely cause?
- The pending Pod's resource requests are too large to fit on a single node of the cluster.
- Too many Pods are already running in the cluster, and there are not enough resources left to schedule the pending Pod.
- The node pool is configured with a service account that does not have permission to pull the container image used by the pending Pod.
- The pending Pod was originally scheduled on a node that has been preempted between the creation of the Deployment and your verification of the Pods' status. It is currently being rescheduled on a new node.
ユーザの投票
コメント(17)
- Correct Answer is (B):
  
  Reasons for a Pod Status Pending: Troubleshooting Reason #1: Not enough CPU Troubleshooting Reason #2: Not enough memory Troubleshooting Reason #3: Not enough CPU and memory https://managedkube.com/kubernetes/k8sbot/troubleshooting/pending/pod/2019/02/22/pending-pod.html
  
  👍 43
  ESP_SAP2020/08/17
- D is correct as the node on which pod was scheduled to run was preempted & now this pod is scheduled to run on different preemtible node from the node-pool
  
  👍 20
  cloudenthu012020/06/25
- 正解だと思う選択肢: D
  D is Right , I think a lot of people discussing here has very low k8s experience . Node pool is a term for refering one or more (usually 4 or more nodes) nodes, you can view nodes as servers that run containers (remember pods are one or more containers) . When one of the nodes from the node pool is down because its a preemtible, all of their pods go down and the kube controller (which is an element running on control plance ) reallocates the pods to other nodes from their node pools and then those pods rill show as running (if the nodes accomplish the resource quotas) . So basically what happend here is that we just did a kubectl get pods command inthe mid time where one of the nodes from the node pool went down and the cluster tried to reposition the pods into other nodes
  
  👍 3
  ashtonez2023/03/09
シャッフルモード

ユーザの投票

コメント(17)