Erich Blume
41dfae1f80
## 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 Reviewed-on: https://forge.ops.eblu.me/eblume/blumeops/pulls/139 |
||
|---|---|---|
| .. | ||
| .gitkeep | ||
| doc-cni-conflict-troubleshooting.doc.md | ||
| docs-power-infrastructure.doc.md | ||
| feature-fly-proxy-error-page.feature.md | ||
| feature-op-backup.feature.md | ||
| feature-sifaka-ops-observability.feature.md | ||
| fix-deploy-healthcheck-race.bugfix.md | ||
| fix-minikube-status-check.bugfix.md | ||
| fix-real-client-ip-logging.bugfix.md | ||
| fix-zero-downtime-deploy.infra.md | ||