Courseiva
Troubleshooting →mediumMultiple Choice

CKA Troubleshooting Practice Question

You try to run 'kubectl logs mypod' and get the error: 'Error from server (BadRequest): container "myapp" in pod "mypod" is waiting to start: PodInitializing'. What does this mean?

⚠ Common exam trap

Test-takers frequently confuse 'PodInitializing' with a crash or restart loop, but the key distinction is that 'PodInitializing' is a transient startup phase, not a failure state, and logs are unavailable until the container actually starts.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

The pod is still being initialized and the container has not started yet.

The error message 'container "myapp" in pod "mypod" is waiting to start: PodInitializing' indicates that the pod's init containers (if any) are still running or the container runtime is pulling the image and setting up the container. The container has not yet entered the 'Running' state, so logs cannot be retrieved until it starts. This is a standard Kubernetes lifecycle phase where the pod is in 'PodInitializing' status, meaning the main container is not ready to serve logs.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✗

    The pod has crashed and is restarting.

    Why it's wrong here

    If a pod has crashed and is restarting, typically indicated by a CrashLoopBackOff status, kubectl logs will still succeed in retrieving logs from the current restarting container or from the previous terminated instance using the --previous flag. It does not block log retrieval with an initialization error because the container has already been created at least once.

  • ✗

    The kubelet is not running on the node.

    Why it's wrong here

    When the kubelet daemon is not running on the node, the control plane cannot communicate with the node's container runtime to fetch logs. Consequently, the pod's status would transition to Unknown, and attempting to retrieve logs would result in a connection timeout or a connection refused error rather than an initialization-specific error.

  • ✗

    The container has a different name than specified.

    Why it's wrong here

    If a pod contains multiple containers and you specify an incorrect container name via the -c flag, the API server returns a specific error stating that the container is not found in the pod specification. This error lists the valid container names available in the pod instead of indicating that the container is waiting to start.

  • ✓

    The pod is still being initialized and the container has not started yet.

    Why this is correct

    This is correct because during the PodInitializing phase, the pod's init containers are still executing, meaning the primary application containers have not yet been created or started by the container runtime. Because the target application container does not exist in a running or terminated state yet, the kubelet cannot stream any log output, resulting in a waiting to start error.

About these practice questions

One of 726 original CKA practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This CKA practice question is part of Courseiva's free CNCF certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CKA exam.