Using Kubernetes I deploy an app to Google Cloud Containerengine on a cluster with 3 smalll instances.

On a first-time deploy, all goes well using:

kubectl create -f deployment.yaml

And:

kubectl create -f service.yaml

Then I change the image in my deployment.yaml and update it like so:

kubectl apply -f deployment.yaml

After the update, a couple of things happen:

• Kubernetes updates its Pods correctly, ending up with 3 updated instances.
• Short after this, another ReplicaSet is created (?)
• Also, the double amount (2 * 3 = 6) of Pods are suddenly present, where half of them have a status of Running, and the other half Unknown.

So I inspected my Pods and came across this error:

FailedSync      Error syncing pod, skipping: network is not ready: [Kubenet does not have netConfig. This is most likely due to lack of PodCIDR]

Also I can't use the dashboard anymore using kubectl proxy. The page shows:

{
  "kind": "Status",
  "apiVersion": "v1",
  "metadata": {},
  "status": "Failure",
  "message": "no endpoints available for service \"kubernetes-dashboard\"",
  "reason": "ServiceUnavailable",
  "code": 503
}

So I decided to delete all pods forecefully:

kubectl delete pod <pod-name> --grace-period=0 --force

Then, three Pods are triggered for creation, since this is defined in my service.yaml. But upon inspecting my Pods using kubectl describe pods/<pod-name>, I see:

no nodes available to schedule pods

I have no idea where this all went wrong. I essence, all I did was updating an image of a deployment.

Anyone ideas?