Cut over remaining service references to Nebula overlay addresses or mesh DNS #23

New issue

Closed

opened 2026-07-01 16:17:21 +01:00 by nimmo · 0 comments

nimmo commented

2026-07-01 16:17:21 +01:00

Owner

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.md records Phases 0–4 and 2.5 as complete. The remaining open work is the service cutover phase.

Acceptance Checklist

Identify the remaining service configs that still use 192.168.8.x addresses.
Replace them with 10.10.0.x overlay addresses or mesh hostnames where appropriate.
Confirm the affected services continue to work both on-LAN and off-LAN through the mesh.
Prefer the Nebula path only where it improves portability and resilience; do not churn working configs without a reason.

Candidate Targets Called Out In The Note

Ollama
NFS consumers
other service configs still pinned to LAN IPs

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.

## 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.md` records Phases 0–4 and 2.5 as complete. The remaining open work is the service cutover phase. ## Acceptance Checklist - Identify the remaining service configs that still use `192.168.8.x` addresses. - Replace them with `10.10.0.x` overlay addresses or mesh hostnames where appropriate. - Confirm the affected services continue to work both on-LAN and off-LAN through the mesh. - Prefer the Nebula path only where it improves portability and resilience; do not churn working configs without a reason. ## Candidate Targets Called Out In The Note - Ollama - NFS consumers - other service configs still pinned to LAN IPs ## 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.

nimmo added this to the Nebula Mesh Network milestone

2026-07-01 16:17:21 +01:00

nimmo added the

project:nebula-mesh-network

host:fleet

labels

2026-07-01 16:17:21 +01:00

nimmo referenced this issue

2026-09-08 08:14:38 +01:00

feat(nebula): cut over service endpoints to mesh #203

nimmo closed this issue

2026-09-10 20:12:23 +01:00