Briefing
A settings rollout for payment went out at 09:20 together with a refresh of its ConfigMap, and the new payment pod has not started since.
The image is the same one that ran yesterday, the pull succeeded, and the kubelet has been retrying for ten minutes and getting nowhere.
Payments are queuing at the gateway while customers watch a spinner.
Dev thinks the kubelet simply has not caught up with the refreshed ConfigMap yet and wants to give it a few more minutes.
The fix is yours to find: hints, the recovery checks and the debrief unlock inside the incident.