Establish a DNS resolver fallback plan for k3s cluster outages #72

Open
opened 2026-07-22 18:38:25 +00:00 by mconway · 0 comments
Owner

Before switching the network's DNS over to Technitium, Pi-hole was an independent appliance with its own uptime story, separate from the k8s cluster. Now the whole LAN's DNS resolution depends on the k3s cluster being healthy.

To decide

  • Is Pi-hole (or anything) still configured as a tertiary/fallback resolver on the router for when Technitium's pods are down (node reboot, k3s upgrade, cluster maintenance, etc.)?
  • If not, what's the plan for that scenario - keep Pi-hole as a documented manual fallback, or something else?

This is an architecture/resilience question, not a bug - just want it explicitly decided rather than discovered during the next cluster maintenance window.

Before switching the network's DNS over to Technitium, Pi-hole was an independent appliance with its own uptime story, separate from the k8s cluster. Now the whole LAN's DNS resolution depends on the k3s cluster being healthy. ## To decide - Is Pi-hole (or anything) still configured as a tertiary/fallback resolver on the router for when Technitium's pods are down (node reboot, k3s upgrade, cluster maintenance, etc.)? - If not, what's the plan for that scenario - keep Pi-hole as a documented manual fallback, or something else? This is an architecture/resilience question, not a bug - just want it explicitly decided rather than discovered during the next cluster maintenance window.
Sign in to join this conversation.
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
mconway/Homelab#72
No description provided.