pod-restart-policy.yaml
apiVersion: v1
kind: Pod
metadata:
name: hello-world-onfailure-pod
spec:
containers:
- name: hello-world
image: gcr.io/google-samples/hello-app:1.0
restartPolicy: OnFailure
---
apiVersion: v1
kind: Pod
metadata:
name: hello-world-never-pod
spec:
containers:
- name: hello-world
image: gcr.io/google-samples/hello-app:1.0
restartPolicy: Never
#Start up kubectl get events --watch and background it.
kubectl get events --watch &
clear
#Create a pod...we can see the scheduling, container pulling and container starting.
kubectl apply -f pod.yaml
#We've used exec to launch a shell before, but we can use it to launch ANY program inside a container.
#Let's use killall to kill the hello-app process inside our container
kubectl exec -it hello-world-pod -- /bin/sh
ps
exit
#We still have our kubectl get events running in the background, so we see if re-create the container automatically.
kubectl exec -it hello-world-pod -- /usr/bin/killall hello-app
#Our restart count increased by 1 after the container needed to be restarted.
kubectl get pods
#Look at Containers->State, Last State, Reason, Exit Code, Restart Count and Events
#This is because the container restart policy is Always by default
kubectl describe pod hello-world-pod
#Cleanup time
kubectl delete pod hello-world-pod
#Kill our watch
fg
ctrl+c
#Remember...we can ask the API server what it knows about an object, in this case our restartPolicy
kubectl explain pods.spec.restartPolicy
#Create our pods with the restart policy
more pod-restart-policy.yaml
kubectl apply -f pod-restart-policy.yaml
#Check to ensure both pods are up and running, we can see the restarts is 0
kubectl get pods
#Let's kill our apps in both our pods and see how the container restart policy reacts
kubectl exec -it hello-world-never-pod -- /usr/bin/killall hello-app
kubectl get pods
#Review container state, reason, exit code, ready and contitions Ready, ContainerReady
kubectl describe pod hello-world-never-pod
#let's use killall to terminate the process inside our container.
kubectl exec -it hello-world-onfailure-pod -- /usr/bin/killall hello-app
#We'll see 1 restart on the pod with the OnFailure restart policy.
kubectl get pods
#Let's kill our app again, with the same signal.
kubectl exec -it hello-world-onfailure-pod -- /usr/bin/killall hello-app
#Check its status, which is now Error too...why? The backoff.
kubectl get pods
#Let's check the events, we hit the backoff loop. 10 second wait. Then it will restart.
#Also check out State and Last State.
kubectl describe pod hello-world-onfailure-pod
#Check its status, should be Running...after the Backoff timer expires.
kubectl get pods
#Now let's look at our Pod statuses
kubectl delete pod hello-world-never-pod
kubectl delete pod hello-world-onfailure-pod
Kubernetes Tutorials using EKS – Part 1 – Introduction and Architecture
Kubernetes Tutorials using EKS – Part 2 – Architecture with Master and worker
Kubernetes Tutorials using EKS – Part 3 – Architecture with POD – RC – Deploy – Service
Kubernetes Tutorials using EKS – Part 4 – Setup AWS EKS Clustor
Kubernetes Tutorials using EKS – Part 5 – Namespaces and PODs
Kubernetes Tutorials using EKS – Part 6 – ReplicationControllers and Deployment
Kubernetes Tutorials using EKS – Part 7 – Services
Kubernetes Tutorials using EKS – Part 8 – Volume
Kubernetes Tutorials using EKS – Part 9 – Volume
Kubernetes Tutorials using EKS – Part 10 – Helm and Networking
I’m a DevOps/SRE/DevSecOps/Cloud Expert passionate about sharing knowledge and experiences. I am working at Cotocus. I blog tech insights at DevOps School, travel stories at Holiday Landmark, stock market tips at Stocks Mantra, health and fitness guidance at My Medic Plus, product reviews at I reviewed , and SEO strategies at Wizbrand.
Please find my social handles as below;
Rajesh Kumar Personal Website
Rajesh Kumar at YOUTUBE
Rajesh Kumar at INSTAGRAM
Rajesh Kumar at X
Rajesh Kumar at FACEBOOK
Rajesh Kumar at LINKEDIN
Rajesh Kumar at PINTEREST
Rajesh Kumar at QUORA
Rajesh Kumar at WIZBRAND
