From fa53b7fee44ecf92f89c7e1bda00a0339bf2f369 Mon Sep 17 00:00:00 2001 From: Nik Afiq Date: Sun, 23 Aug 2026 11:40:26 +0900 Subject: [PATCH] fix: disable both Pi-hole instances during DNS migration Set replicaCount: 0 for pihole and pihole-debian so Argo CD's selfHeal doesn't scale them back up once its git connectivity recovers. Live deployments already scaled to 0 directly; this just keeps git in sync with that so it sticks. Co-Authored-By: Claude Sonnet 5 --- values/pihole-debian.yaml | 2 +- values/pihole.yaml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/values/pihole-debian.yaml b/values/pihole-debian.yaml index 9b03f9f..cfde2e2 100644 --- a/values/pihole-debian.yaml +++ b/values/pihole-debian.yaml @@ -1,7 +1,7 @@ # Apply: helm upgrade --install pihole-debian mojo2600/pihole -f values/pihole-debian.yaml -n pihole --create-namespace # Description: Helm values for Pi-hole secondary instance on Debian node -replicaCount: 1 +replicaCount: 0 nodeSelector: node-role: storage diff --git a/values/pihole.yaml b/values/pihole.yaml index d6a7410..9b13f8d 100644 --- a/values/pihole.yaml +++ b/values/pihole.yaml @@ -1,7 +1,7 @@ # Apply: helm upgrade --install pihole mojo2600/pihole -f values/pihole.yaml -n pihole --create-namespace # Description: Helm values for Pi-hole DNS server on Minisforum -replicaCount: 1 +replicaCount: 0 image: tag: "2024.07.0"