I'll keep this brief -- here's a reminder on the various ways that Kubernetes can manage pods:

• Kubernetes Deployment - The most common way to deploy containerized applications. This approach lets you control the number of replicas running. When you have a new version of the application running, Kubernetes can keep the old version up and smoothly deploy the new ones before removing the old pods. This is a no-downtime upgrade.
• DaemonSet - This puts one pod on every node running in the cluster, so you can't directly control the numbers of replicas running. DaemonSets usually run containers that are agents (or Daemons) running processes in the background.
  
• Kubernetes Job - A job will create one or more pods and run the container inside of them until it has successfully completed its task.