A release includes a breaking schema change that cannot safely mix v1 and v2 Pods behind the same Service. Which deployment approach is most appropriate?
Select an answer to reveal the explanation.
Short Explanation
If v1 and v2 speak different database dialects, don’t seat them at the same table mid-meal. Blue/green or recreate avoids the mixed-version window that rolling updates create. maxSurge just invites more mixing.
Full Explanation
Rolling updates intentionally run old and new Pods concurrently. When versions are incompatible (for example, breaking schema assumptions), blue/green cutover or a recreate strategy avoids mixed serving. Tuning surge or pull policy does not remove the compatibility problem.