A release candidate is promoted from staging with the right image digest, but...

시나리오

The artifact is correct, yet behavior differs because runtime …

단서

구독하면 이어서 볼 수 있어요

이 문제의 전체 시나리오와 점검 체크리스트, 복구 순서, 모범 풀이는 Pro 구독에서 열립니다.

구독 안내 보기

먼저 볼 것

점검 체크리스트

복구와 재발 방지

같이 보면 좋은 질문

현장에서 본 비슷한 케이스

다음으로 이어서 보기 좋은 문제

CI/CD Advanced

A rollback restores application code while feature migration flags remain enabled in the old environment during a failover rehearsal

The binary path moves backward and the runtime behavior still follows the newer feature contract. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.

19 min

View problem

CI/CD Advanced

A deployment circuit breaker watches the startup probe, but the one-off migration pod shares the same label and trips the release incorrectly

Application pods are healthy, yet rollout halts because the failure budget includes a different workload type with a separate lifecycle.

17 min

View problem

CI/CD Advanced

A rollout job waits for one migration task while a second schema-affecting job starts from another workflow in parallel during a failover rehearsal

The database change path appears serialized, yet another automation lane mutates the same contract at the same time. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.

19 min

View problem

CI/CD Advanced

A migration approval checks the application schema version while one asynchronous worker still runs the old reader contract in parallel during a staged decommission

The release gate inspects the main service and misses the parallel consumer that still depends on the old shape. The service still works through the primary path, but one dependency only fails when the old component is finally drained away.

17 min

View problem

A release candidate is promoted from staging with the right image digest, but the production values file still points at the old feature-flag namespace

A rollback restores application code while feature migration flags remain enabled in the old environment during a failover rehearsal

A deployment circuit breaker watches the startup probe, but the one-off migration pod shares the same label and trips the release incorrectly

A rollout job waits for one migration task while a second schema-affecting job starts from another workflow in parallel during a failover rehearsal

A migration approval checks the application schema version while one asynchronous worker still runs the old reader contract in parallel during a staged decommission