Question

A new engineer on your team wants to run 3 replicas of a stateless web application. They created a ReplicaSet manifest directly (not a Deployment) and applied it. Later they need to update the container image to a new version. What limitation will they encounter with this approach?

Accepted Answer

The ReplicaSet does not manage rolling updates or revision history, so changing the image requires manually deleting Pods to have them recreated

Answer

The ReplicaSet will automatically roll out the new image with zero downtime once the manifest is updated

Answer

The ReplicaSet will reject the update because container images are immutable once a ReplicaSet is created

Answer

The ReplicaSet will scale to zero and require a full recreation of the object before any image change is allowed