coilyco-flight-deck/infrastructure
2
0
Fork 0
Code Issues 118 Pull requests Projects Releases Packages Wiki Activity Actions 2

Register ntfy tailnet device in tailscale-devices terraform #14

New issue
Closed
opened 2026-05-23 20:54:27 +00:00 by coilysiren · 1 comment
coilysiren commented 2026-05-23 20:54:27 +00:00
Owner
Copy link

Originally filed by @coilysiren on 2026-05-22T13:05:02Z - https://github.com/coilysiren/infrastructure/issues/272

What - Register ntfy as a tailnet sidecar device in the terraform/tailscale-devices/ module.

ntfy is now listed in that module's services.yaml services list. A terraform apply of the module mints one tailscale_tailnet_key tagged tag:k8s and writes it to SSM at /coilysiren/ntfy/ts-authkey.

Scope - this issue covers device registration only. The key parks in SSM until ntfy gets a Deployment with a tailscale sidecar plus an ExternalSecret consuming that path. The ntfy deployment itself is separate, later work.

_Originally filed by @coilysiren on 2026-05-22T13:05:02Z - [https://github.com/coilysiren/infrastructure/issues/272](https://github.com/coilysiren/infrastructure/issues/272)_ **What** - Register `ntfy` as a tailnet sidecar device in the `terraform/tailscale-devices/` module. `ntfy` is now listed in that module's `services.yaml` services list. A `terraform apply` of the module mints one `tailscale_tailnet_key` tagged `tag:k8s` and writes it to SSM at `/coilysiren/ntfy/ts-authkey`. **Scope** - this issue covers device registration only. The key parks in SSM until `ntfy` gets a Deployment with a tailscale sidecar plus an ExternalSecret consuming that path. The ntfy deployment itself is separate, later work.
coilysiren commented 2026-06-17 08:22:59 +00:00
Author
Owner
Copy link

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: burndown-2026-06.

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: `burndown-2026-06`.
coilysiren 2026-06-17 08:22:59 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
issue-515
issue-486
issue-529
issue-500
issue-483
No results found.
Labels
Clear labels   
burndown-2026-06
Backlog burndown June 2026

  
coherence-core
Core review set for the warded control plane coherence milestone. These issues form the release spine; adjacent milestone issues are stretch or supporting work.

  
consult
A human decision, design, or external action must happen first. Fail-closed default for unlabeled/low-confidence.

  
headless
Agent can take it from open issue to merged change with no human in the loop. The auto-burndown queue.

  
interactive
Agent does the work but pauses at a human checkpoint mid-flight (design choice, destructive step, human-only verification).

  
P0
now / blocking / urgent

  
P1
next / important

  
P2
backlog / will do

  
P3
someday / low

  
P4
icebox / frozen / reopen if it becomes real

No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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
coilyco-flight-deck/infrastructure#14
No description provided.