Skip to content

Update cutover.md #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dfredriksen merged 1 commit into from
Jul 3, 2026
Merged

Update cutover.md #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 0 additions & 30 deletions docs/cutover.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,31 +1 @@
# Tailscale Cutover

Dragonscale must roll out in parallel with Tailscale until private Kuzuryu access is verified.

## Cutover Order

1. Deploy Dragonscale at `https://dragonscale.kuzuryu.ai`.
2. Register Dan's laptop.
3. Register the Kuzuryu host.
4. Verify laptop-to-Kuzuryu private service access over Dragonscale.
5. Register the Hawaii Surface.
6. Add Noah after his exact Google account is confirmed.
7. Move `orchestrator.kuzuryu.ai` from the old Tailscale IP to the Dragonscale address only after validation.
8. Keep Tailscale installed but deprioritized until one full operating day passes without access issues.

## Rollback

If Dragonscale fails:

- leave `orchestrator.kuzuryu.ai` on the current Tailscale address
- keep public `kuzuryu.ai` and `boards.kuzuryu.ai` unchanged
- stop the Dragonscale container
- preserve `/opt/dragonscale/data` for analysis

## Completion Criteria

- Dan laptop can authenticate through Google OAuth.
- Kuzuryu host appears in `headscale nodes list`.
- Hawaii Surface can join and reach the private Kuzuryu service.
- Unauthorized Google account cannot join.
- Tailscale is still available as rollback.
Loading