CODEWITHSUNDEEP
javaazurekubernetesfabric8
user_mda
user_mda

Reputation: 19418

Pods stuck in pending state

I am using the Kubernetes-client java client to create Deployments on a Kubernetes cluster. THis is the code

Deployment deployment = new DeploymentBuilder()
        .withNewMetadata()
        .withName("first-deployment")
        .endMetadata()
        .withNewSpec()
        .withReplicas(3)
        .withNewTemplate()
        .withNewMetadata()
        .addToLabels(namespaceID, "hello-world-example")
        .endMetadata()
        .withNewSpec()
        .addNewContainer()      
        .withName("nginx-one")
        .withImage("nginx")
        .addNewPort()
        .withContainerPort(80)
        .endPort()
        .withResources(resourceRequirements)
        .endContainer()
        .endSpec()
        .endTemplate()
        .endSpec()
        .build();
    deployment = client.extensions().deployments().inNamespace(namespace).create(deployment);

I add a3 min wait time and then test the status of the pod

PodList podList = client.pods().withLabel(namespaceID, "hello-world-example").list();
    System.out.println("Number of pods " + podList.getItems().size());
    for (Pod pod : podList.getItems()) {
        System.out.println("Name " + pod.getMetadata().getName() 
            + " Status " + pod.getStatus().getPhase() 
            + " Reason " + pod.getStatus().getReason()
        + " Containers " + pod.getSpec().getContainers().get(0).getResources().getLimits());

    }

This returns the following sttaus

Name first-deployment-2418943216-9915m Status Pending Reason null Containers null
Name first-deployment-2418943216-fnk21 Status Pending Reason null Containers null
Name first-deployment-2418943216-zb5hr Status Pending Reason null Containers null

However from the commandline if I get kubectl get pods --all-namespaces. It returns the pod state as running . Am I using the right API? what did I miss?

Upvotes: 12

Views: 1305

Answers (2)

Swapnil B.
Swapnil B.

Reputation: 120

Not sure if this question is still open, but I would suggest to use something like this: https://github.com/kubernetes/helm/blob/d790f7d843182f1c126cfa64989ffdd4e9583747/pkg/kube/wait.go#L174

It loops through deployments, and wait till max available from manifest.

Upvotes: 1

fatcook
fatcook

Reputation: 1026

Maybe a better way to check this is to have a loop and sleep inside to loop and continuously keep checking the status until all pods are up are running. I had done something similar to check if all the required pods were up by checking the status. But you might also want to consider adding the liveness and readiness probe on the pods before you make such a check. There are additional details provided here.

https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/

Upvotes: 2

Related Questions