Transit fare API owners change the OCIR image tag on an OKE Deployment and want riders to keep hitting ready Pods during the cutover. Which strategy should they keep?
Select an answer to reveal the explanation.
Short Explanation
RollingUpdate is like swapping bus doors one at a time while the route stays open. Recreate is closing the whole garage first. On OKE, RollingUpdate is the professional default so the Service keeps selecting ready Pods through the cutover.
Full Explanation
Changing a Deployment Pod template (new OCIR tag or env) triggers the strategy. RollingUpdate brings new Pods up and retires old ones while the Service continues to select ready endpoints. Recreate tears all Pods down first and causes a brief outage. Scaling to zero or deleting the Service invents downtime the Deployment already knows how to avoid. Keep RollingUpdate for a live transit fare API.