Skip to content

feat(adguard): deploy adguardhome-sync for cross-cluster config sync#1450

Open
ixxeL2097 wants to merge 1 commit into
mainfrom
feat/adguard-ha-sync
Open

feat(adguard): deploy adguardhome-sync for cross-cluster config sync#1450
ixxeL2097 wants to merge 1 commit into
mainfrom
feat/adguard-ha-sync

Conversation

@ixxeL2097

Copy link
Copy Markdown
Member

Summary

  • Deploys bakito/adguardhome-sync v0.9.0 in the adguard namespace on genmachine
  • Existing AdGuard Home deployment is untouched (still 3 replicas, same PVC)
  • Sync runs every 2 minutes: genmachine adguard (origin) → beelink adguard adguard.k0s-fullstack.fredcorp.com (replica)
  • Synced: DNS rewrites, filters, blocked services, upstream DNS config

New resources

Resource Kind Purpose
adguardhome-sync-config ConfigMap Sync config (origin/replica URLs, cron)
adguardhome-sync-credentials ExternalSecret Fetches plaintext credentials from Vault
adguardhome-sync Deployment Runs the sync loop

Prerequisite: Vault secret

The ExternalSecret pulls from Vault path adguard/credentials. This key must be populated before ArgoCD syncs:

vault kv put adguard/credentials username=admin password=<plaintext-admin-password>

Test plan

  • Vault key adguard/credentials populated with plaintext admin password
  • adguardhome-sync-credentials Secret created successfully by ExternalSecret
  • adguardhome-sync pod Running
  • Logs show successful sync: sync completed
  • DNS rewrite change on genmachine propagates to beelink within ~2 minutes

🤖 Generated with Claude Code

… and beelink

Deploys bakito/adguardhome-sync alongside the existing AdGuard Home instances.
Syncs DNS rewrites, filters and settings from genmachine (origin) to beelink (replica)
every 2 minutes. Credentials are sourced from Vault via ExternalSecret at adguard/credentials.

Prerequisite: populate Vault key adguard/credentials with username and password (plaintext)
matching the AdGuard admin account.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@ixxeL2097 ixxeL2097 force-pushed the main branch 10 times, most recently from 99be2b4 to 0ff926a Compare April 26, 2026 19:16
@ixxeL2097 ixxeL2097 force-pushed the main branch 3 times, most recently from 5248ff3 to 5c29049 Compare May 14, 2026 06:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant