Establish a DNS resolver fallback plan for k3s cluster outages #72
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
This is an architecture/resilience question, not a bug - just want it explicitly decided rather than discovered during the next cluster maintenance window.