Add CNI conflict troubleshooting to restart-indri how-to #139

Merged
eblume merged 1 commit from doc/cni-conflict-troubleshooting into main 2026-02-10 07:24:43 -08:00
Owner

Summary

  • Documents a troubleshooting procedure for broken pod networking after unclean shutdown
  • During minikube recovery, a stale 1-k8s.conflist CNI config can override kindnet's 10-kindnet.conflist, causing new pods to use bridge+firewall networking instead of kindnet's ptp — breaking pod-to-pod communication
  • Covers symptoms (DNS failures, liveness probe timeouts), diagnosis steps, and the fix

Context

Encountered this during the 2026-02-10 power outage. Immich, kiwix, and transmission were all crash-looping for ~8 hours due to the CNI conflict. The minikube ansible role's clean boot detection has been improved (#137) so this may not recur, but the troubleshooting guide is valuable if it does.

Test plan

  • Documentation only — no code changes
  • Pre-commit hooks pass
## Summary - Documents a troubleshooting procedure for broken pod networking after unclean shutdown - During minikube recovery, a stale `1-k8s.conflist` CNI config can override kindnet's `10-kindnet.conflist`, causing new pods to use bridge+firewall networking instead of kindnet's ptp — breaking pod-to-pod communication - Covers symptoms (DNS failures, liveness probe timeouts), diagnosis steps, and the fix ## Context Encountered this during the 2026-02-10 power outage. Immich, kiwix, and transmission were all crash-looping for ~8 hours due to the CNI conflict. The minikube ansible role's clean boot detection has been improved (#137) so this may not recur, but the troubleshooting guide is valuable if it does. ## Test plan - [x] Documentation only — no code changes - [x] Pre-commit hooks pass
After an unclean shutdown, minikube recovery can regenerate a stale
1-k8s.conflist CNI config that overrides kindnet, breaking pod
networking for newly created pods. Document symptoms, diagnosis
steps, and the fix.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
eblume merged commit 41dfae1f80 into main 2026-02-10 07:24:43 -08:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
eblume/blumeops!139
No description provided.