Imagine we'd have to manually launch hundreds of containers on many different servers. It wouldn't be fun, and it would take a long time. But Kubernetes makes such a task almost easy. We write one YAML manifest file, and tell it we want to run 100 containers on 5 different servers; the job is done! It will automatically launch them for us. But what happens when we want to change something in such a set of logically grouped containers? How do we make sure that change is propagated in a non-disruptive way?
This is a companion discussion topic for the original entry at https://kodekloud.com/blog/kubernetes-deployments/