Depending on where you look first, you might face other issues. The examples below illustrate how the same issue could look when using other commands.
- The old and new Deployment are in
Running
state. kubectl get deployment
NAME READY UP-TO-DATE AVAILABLE AGE
webapp 1/1 1 1 29m
kubectl get pods
NAME READY STATUS RESTARTS AGE
webapp-849f69665c-hw4t4 1/1 Running 0 29m
webapp-84b785f954-r49wt 2/2 Running 0 29m
- The command
kubectl get pods -o wide
shows that the Pod is not yet ready. kubectl get pods -o wide
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
webapp-849f69665c-hw4t4 1/1 Running 0 32m 10.43.1.173 worker-0 <none> <none>
webapp-84b785f954-r49wt 2/2 Running 0 32m 10.43.2.173 worker-1 <none> 0/1
- The
Readiness
and Liveness probes
failed. kubectl describe pod webapp-84b785f954-r49wt
...
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
...
Warning Unhealthy 50m (x2 over 50m) kubelet Liveness probe failed: Get "http://10.43.2.173:19001/ready": dial tcp 10.43.2.173:19001: connect: connection refused
Warning Unhealthy 50m (x2 over 50m) kubelet Readiness probe failed: Get "http://10.43.2.173:19001/ready": dial tcp 10.43.2.173:19001: connect: connection refused