Init container cascade when every kubectl patch reverts in 10 seconds
6d ago · 10 min read · The Slack ping came in at 2:14 am. Two replicas of the fanout service were stuck in Init:1/3 and the deploy queue behind them had grown to seven changes. The on-call engineer had already tried the obv
Join discussion
















