From 64cf99121cbb1fd4fd21f34d78659365f45d9af2 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Mats=20T=C3=B6rnberg?= <mats.tornberg@gmail.com>
Date: Mon, 28 Sep 2026 15:13:49 +0200
Subject: [PATCH] Enable console-managed Kubernetes zones

The Kubernetes config left blocklist.managed_zones empty, so the Zones page was read-only even though the pod has a writable persistent data volume. Configure a managed-zone directory on that volume so the console can create and update zone records; existing local_zones files remain operator-owned and read-only.
---
 deploy/k8s/00-config.yaml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/deploy/k8s/00-config.yaml b/deploy/k8s/00-config.yaml
index 411151e..cfdea52 100644
--- a/deploy/k8s/00-config.yaml
+++ b/deploy/k8s/00-config.yaml
@@ -81,6 +81,7 @@ data:
     blocklist:
       enabled: true
       default_action: nxdomain
+      managed_zones: /var/lib/fancy-dns/managed-zones
       local_zones: [/etc/fancy-dns/zones/*.zone]
       lists:
         - name: haas