In Kubernetes, what is a deployment?

In Kubernetes, what is a deployment?

• A. A deployment stores configuration files.
• B. A deployment is the physical server hardware.
• C. A deployment manages replicas and rollout of pods.
• D. A deployment is a single container image.

Answer: (C)

In Kubernetes, a deployment is a controller that maintains the desired state for an application by managing how many copies of your pods run and how updates are rolled out. You declare the number of replicas and the container image in the deployment, and Kubernetes ensures that exactly that many pods are running. When you change the deployment (like updating the image), it performs a rolling update, gradually replacing old pods with new ones while keeping the app available. If something goes wrong, you can roll back to a previous revision. It doesn’t store configuration files—that’s what ConfigMaps or Secrets are for. It isn’t physical server hardware. And it isn’t a single container image—the deployment governs potentially many pods, all working together to run the app.

In Kubernetes, a deployment is a controller that maintains the desired state for an application by managing how many copies of your pods run and how updates are rolled out. You declare the number of replicas and the container image in the deployment, and Kubernetes ensures that exactly that many pods are running. When you change the deployment (like updating the image), it performs a rolling update, gradually replacing old pods with new ones while keeping the app available. If something goes wrong, you can roll back to a previous revision.

It doesn’t store configuration files—that’s what ConfigMaps or Secrets are for. It isn’t physical server hardware. And it isn’t a single container image—the deployment governs potentially many pods, all working together to run the app.