A pod restart budget is healthy, but the cluster autoscaler removes the only...

시나리오

Capacity remains, yet storage locality still …

단서

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

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

구독 안내 보기

먼저 볼 것

점검 체크리스트

복구와 재발 방지

같이 보면 좋은 질문

현장에서 본 비슷한 케이스

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

K8s Advanced

A local storage workload looks healthy until scale-down removes the only node that satisfies its locality during a failover rehearsal

Compute capacity remains while schedulability disappears because the data stayed behind. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.

18 min

View problem

K8s Advanced

A StatefulSet ordinal comes back with a recycled PVC name while one sidecar still pins the old pod identity during a failover rehearsal

Storage is healthy, yet one companion process keeps talking to the stateful member as if it were the previous ordinal instance. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.

19 min

View problem

K8s Advanced

A StatefulSet restore brings back volume data while one ordinal-specific peer identity still points at the pre-failover cluster member during a failover rehearsal

The data is back, but the peer relationship model remains attached to the old identity. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.

19 min

View problem

K8s Advanced

A mutating webhook injects runtime labels that a later affinity rule needs, but scheduling decisions happen before those labels exist during a failover rehearsal

The final pod metadata looks correct while initial placement decisions were made without it. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.

19 min

View problem

A pod restart budget is healthy, but the cluster autoscaler removes the only node with local PV affinity and the replacement pod cannot reschedule

A local storage workload looks healthy until scale-down removes the only node that satisfies its locality during a failover rehearsal

A StatefulSet ordinal comes back with a recycled PVC name while one sidecar still pins the old pod identity during a failover rehearsal

A StatefulSet restore brings back volume data while one ordinal-specific peer identity still points at the pre-failover cluster member during a failover rehearsal

A mutating webhook injects runtime labels that a later affinity rule needs, but scheduling decisions happen before those labels exist during a failover rehearsal