nik/homelab
1
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: disable both Pi-hole instances during DNS migration
Some checks failed
validate / lint (push) Has been cancelled
Details

Browse Source 
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 <noreply@anthropic.com>
This commit is contained in:
Nik Afiq 2026-08-23 11:40:26 +09:00
parent 12b3b48e8d
commit fa53b7fee4
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
values/pihole-debian.yaml
View File

@ -1,7 +1,7 @@
# Apply: helm upgrade --install pihole-debian mojo2600/pihole -f values/pihole-debian.yaml -n pihole --create-namespace # 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 # Description: Helm values for Pi-hole secondary instance on Debian node
replicaCount: 1 replicaCount: 0
nodeSelector: nodeSelector:
node-role: storage node-role: storage

2
values/pihole.yaml
View File

@ -1,7 +1,7 @@
# Apply: helm upgrade --install pihole mojo2600/pihole -f values/pihole.yaml -n pihole --create-namespace # 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 # Description: Helm values for Pi-hole DNS server on Minisforum
replicaCount: 1 replicaCount: 0
image: image:
tag: "2024.07.0" tag: "2024.07.0"