Jobs and CronJobs in Kubernetes

#kubernetes #jobs #cronjobs #devops #fullstackdevelopment

I’m sure that you have come across different controllers for managing pods like Replicasets, Deployments, Statefulsets, and Daemonsets. These all controllers ensure that their pods are always running. If a pod fails, the controller restarts it or reschedules it to another node to make sure the desired no.of pods is always running.

But, what if we want to run our pods only once like for taking the DB backup, or sending emails in a batch? Such processes should not be running continuously. They’ll run for a certain amount of time and they run at particular times, not continuously. For these processes, having controllers like deployment is a bad idea as it makes sure the pod runs continuously!

In this video, we’ll learn how to run batch jobs only once or schedule them at particular intervals, using Jobs and CronJobs with complete hands-on!

Manifests: https://github.com/pelthepu/Kubernete...

Please give a Like and Subscribe to the channel - https://bit.ly/pavanelthepu

Timestamps:
0:00 - Intro
01:06 - Job Lifecycle
03:28 - CronJob
04:23 - Usecases
05:04 - MongoDB Backup with Job
10:24 - MongoDB Backup with CronJob

My other courses:
Docker Complete Course:    • Docker Tutorial |  Full Course in 2 Hours  

Thank you very much!