Daemonsets, Job & Cronjob in — Kubernetes

A DaemonSet is a Kubernetes resource that ensures that a specific pod runs on every node in the cluster. It's commonly used to deploy system daemons (or) cluster-wide services that should be available on every node. Key characteristics of a DaemonSet: One Pod Per Node Automated Deployment and Scaling Node Selector and Affinity Update Strategies A basic example of a DaemonSet manifest: Let's create a Daemon.yml file and save it in our file system. apiVersion: apps/v1 kind: DaemonSet metadata: name: demo-ds labels: name: demo-ds spec: template: metadata: labels: name: demo-ds spec: containers: - name: nginx-ds image: nginx selector: matchLabels: name: demo-ds Go to the directory where the file is located and run the below command. kubectl apply -f Daemon.yml This will create a DaemonSet, and you will see one pod created per node. To view all DaemonSets in the cluster kubectl get ds -A To view DaemonSets in a specific namespace: kubectl get ds -n kubectl get ds -n default Cronjob and Jobs Job → Runs immediately and performs a one-time task without scheduling. CronJob → Runs Jobs on a schedule, ideal for recurring tasks. Jobs A Job in Kubernetes is a resource to create one (or) more pods that run a specific task and ensure completion. Once a Job is completed successfully, all its associated pods terminate. Jobs are typically used for batch processing, data migration…

Always learning