Cut over remaining service references to Nebula overlay addresses or mesh DNS #23
Labels
No labels
host:electra
host:fleet
host:lyra
host:vega
host:vega
phase:cutover
phase:deploy
phase:mcp
phase:module
phase:packaging
phase:prep
phase:validation
project:attic-postgres-lyra-rollout
project:auto-update-reliability
project:declarative-purity-cleanup
project:external-review
project:host-facts-refactor
project:lyra-nixos-deploy
project:lyra-service-stack-migration
project:nebula-mesh-network
project:security-hardening
project:service-stack-migration
project:vega-sillytavern-cutover
service:auto-update
service:mem0
service:sillytavern
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
nimmo/nixos-config#23
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Goal
Complete Phase 5 of the Nebula rollout by replacing remaining hardcoded LAN addresses with Nebula overlay addresses or mesh hostnames.
Context
projects/nebula-mesh-network.mdrecords Phases 0–4 and 2.5 as complete. The remaining open work is the service cutover phase.Acceptance Checklist
192.168.8.xaddresses.10.10.0.xoverlay addresses or mesh hostnames where appropriate.Candidate Targets Called Out In The Note
Verification
End-to-end checks should confirm that existing service access still works after the address change, including at least one cross-host access path over the mesh.