---
# Your internal domain used by Samba AD (split-horizon is fine)
prole_domain: "prole.org"

# Samba AD DC IP
ad_dc_ip: "10.0.0.3"

# Reverse zone for 10.0.0.0/24
lan_reverse_zone: "0.0.10.in-addr.arpa"

# Performance/resilience knobs
pihole_dns_forward_max: 300
pihole_sqlite_busy_timeout: 5000

# knoe.dev GKE service records — resolved on the LAN via dnsmasq address= directives.
# These bypass split-horizon Samba DNS which only knows prole.org, not knoe.dev.
# GCE LB IPs are stable (manually assigned via GCP static IP reservation).
#
# To update: change the IP below and re-run the pihole_dns role.
# Source of truth: `kubectl get ingress -A` on the knoe-dev-0 cluster.
knoe_dev_dns_records:
  # knoe-mcp: company knowledge MCP  (GCE LB: knoe-mcp-knoeledge-mcp)
  - { name: "mcp.0.knoe.dev",    ip: "8.232.93.14"  }
  # knoe-auth: identity / OIDC / Kerberos token exchange  (GCE LB: knoe-auth)
  - { name: "auth.0.knoe.dev",   ip: "34.36.71.141"  }
  # supabase kong: API gateway + DB proxy  (GCE LB: supabase-kong)
  - { name: "api.0.knoe.dev",    ip: "34.120.221.5"  }
  - { name: "db.0.knoe.dev",     ip: "34.120.221.5"  }
  # Knoey web app
  - { name: "app.0.knoe.dev",    ip: "34.120.221.5"  }