Kubernetes Deployment vs Deployment (Software)
People read a Kubernetes Deployment as the act of deploying, and it is not that. Deploying is the act of putting a new version live, by any means. A Kubernetes Deployment is a saved setting in a cluster. It keeps a set number of pods running and swaps them in when the image changes.
Kubernetes Deployment
A Kubernetes setting that keeps a set number of pods up. It swaps them in safely.
A Kubernetes deployment keeps a set number of matching pods running. You say which image to use and how many copies you want. If a pod dies, the deployment makes a new one. When you change the image, it swaps old pods for new ones a few at a time. If the new version goes wrong, you can roll back to the last one.
Deployment (Software)
Putting a new version of your app on the servers. Then users get it.
Deployment is putting a new version of your software onto the servers where it runs. It copies the build there, sets it up and switches traffic to it. A deploy can go to staging for testing or to production for real users. Good teams make it one command, done by a machine. A deploy is not always a release, since new code can be shipped but kept hidden.
In one line
- Kubernetes Deployment
- A Kubernetes setting that keeps a set number of pods up. It swaps them in safely.
- Deployment (Software)
- Putting a new version of your app on the servers. Then users get it.
These live in different corners of the glossary (Infrastructure and Development), which is exactly why they get confused.