ShieldGate Docs

Deploy

Redis multi-proxy sync

Hot-reload configuration across many data-plane nodes.

Goal

Scale Proxies horizontally with consistent config.

How it works

  1. Control plane publishes a snapshot and bumps ConfigVersion.
  2. Redis publishes on shieldgate:config:{tenantId} (and optionally …:all).
  3. Each Proxy pulls the snapshot over the internal API and atomically swaps runtime state.

Steps

  1. Set Redis:Enabled=true and a shared connection string on Api, Worker, and all Proxies.
  2. Use the same DataPlane:InternalApiKey everywhere.
  3. Deploy N Proxy replicas with the same TenantId (or shard by tenant with dedicated fleets).
  4. Publish a change; confirm every replica’s /ready version matches.

Verify

  • Pub/sub message received (Proxy logs).
  • No restart required for policy/route updates.

Pitfalls

  • Without Redis, proxies still load on startup/pull but will not get live notifications.
  • Split-brain keys across Redis DBs cause silent missed updates.