feat(config-push): regen-on-move — re-push peer-baked configs on member.ip_changed #170

Merged
charles merged 1 commit from feat/config-regen-on-move into main 2026-08-31 04:49:50 +00:00
Owner

Task #3, completes the dynamic-IP mechanism. On member.ip_changed, re-push the members whose config bakes the moved member IP: dns/recursor→view re-push (dnsdist backends/forward/ACLs), metrics→dist rebuild (VM endpoint; live for wave-1), dhcp→Kea HA re-push. Leaf roles no-op. Tests: 3 pass.

🤖 Generated with Claude Code

Task #3, completes the dynamic-IP mechanism. On member.ip_changed, re-push the members whose config bakes the moved member IP: dns/recursor→view re-push (dnsdist backends/forward/ACLs), metrics→dist rebuild (VM endpoint; live for wave-1), dhcp→Kea HA re-push. Leaf roles no-op. Tests: 3 pass. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
When a floated member's lattice IP changes (member-IP-refresh loop emits
member.ip_changed), the member itself is reached at its refreshed
docker_bridge_ip, but OTHER members whose generated config BAKES its IP as a
peer must be re-pushed:
- dns/recursor move → debounced full view re-push (rebuilds dnsdist newServer
  backends, the recursor→auth forward target, and dns AXFR/NOTIFY ACLs).
- metrics move → rebuild dist (dnsdist bakes the VictoriaMetrics remote-write
  endpoint) — needed for wave-1 (metrics is already floated).
- dhcp move → re-push dhcp (Kea HA peer configs reference the peer's IP).
- dist/ui/logs/database/discovery bake no peer's IP → no regen.

Completes the dynamic-IP mechanism: float (role-scoped) + keep docker_bridge_ip
fresh (IP-refresh loop) + regen peer-baked configs (this). Inert for pinned
roles; the metrics branch is live for the floated wave-1.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EPmYfmPxMNCcd47mNUPmH9
charles deleted branch feat/config-regen-on-move 2026-08-31 04:49:50 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
charles/projectoctet!170
No description provided.