A DevOps engineer must roll out version 2.1 of a customer-facing web API that currently runs as a Kubernetes Deployment with four replicas behind a ClusterIP Service. Management states that users should not notice any interruption while the new container image is introduced. Which Kubernetes deployment strategy should the engineer use to satisfy this requirement?
Select the RollingUpdate strategy so that pods are replaced gradually while at least some replicas stay available
Use the Recreate strategy, which terminates all old pods before starting any new pods
Trigger a force redeploy by deleting the Deployment object and immediately applying the new manifest
Choose an OnDelete update strategy so that only manually deleted pods are recreated with the new version
RollingUpdate incrementally creates pods that use the new image and waits until each is reported as Ready before scaling down the older replica set. Because at least some replicas remain available throughout the rollout, the Service can continue routing traffic, resulting in a zero-downtime release. The Recreate strategy stops all existing pods first, producing an outage. Deleting and re-applying the Deployment object briefly leaves no pods at all. The OnDelete strategy only updates pods after they are manually removed, so service gaps can occur while old pods are gone and new ones have not yet started.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What are the main differences between RollingUpdate and Recreate strategies in Kubernetes?
Open an interactive chat with Bash
How does a ClusterIP Service interact with a Kubernetes Deployment during a RollingUpdate?
Open an interactive chat with Bash
What is the purpose of the 'Ready' status in Kubernetes during a RollingUpdate?