coilyco-flight-deck/infrastructure

Watch

registries.yaml only on kai-server, not fleet-wide #171

New issue

Closed

opened 2026-05-28 12:31:47 +00:00 by coilysiren · 1 comment

coilysiren commented

2026-05-28 12:31:47 +00:00

Owner

Follow-up caveat from the in-cluster registry bring-up (#168, channel Q9WR).

/etc/rancher/k3s/registries.yaml (the insecure entry for 192.168.0.194:30500) was placed on kai-server only. The other nodes (kai-desktop-tower-wsl, kai-macbook-pro-vm) do not have it.

Not breaking today: the app pods that pull from the registry are pinned to kai-server via nodeSelector (the ts sidecar needs /dev/net/tun on native Linux). The forgejo runner on the WSL node only pushes via its DinD --insecure-registry flag, it does not pull through containerd.

Risk: if any deployable pod schedules on the WSL or VM node, its pull from 192.168.0.194:30500 would fail. Decide whether to replicate registries.yaml fleet-wide or keep app pods pinned to kai-server.

Reported by claude-linux-kai-server-b41d via agent channel Q9WR (comms #67).

Follow-up caveat from the in-cluster registry bring-up (#168, channel Q9WR). `/etc/rancher/k3s/registries.yaml` (the insecure entry for 192.168.0.194:30500) was placed on **kai-server only**. The other nodes (kai-desktop-tower-wsl, kai-macbook-pro-vm) do not have it. Not breaking today: the app pods that pull from the registry are pinned to kai-server via nodeSelector (the ts sidecar needs /dev/net/tun on native Linux). The forgejo runner on the WSL node only **pushes** via its DinD --insecure-registry flag, it does not pull through containerd. Risk: if any deployable pod schedules on the WSL or VM node, its pull from 192.168.0.194:30500 would fail. Decide whether to replicate registries.yaml fleet-wide or keep app pods pinned to kai-server. Reported by claude-linux-kai-server-b41d via agent channel Q9WR (comms #67).

coilysiren added the

priority

label

2026-06-04 08:16:53 +00:00

coilysiren added

priority

and removed

priority

labels

2026-06-17 08:40:15 +00:00

coilyco-ops added

and removed

labels

2026-07-09 21:46:40 +00:00

coilysiren removed the

autonomy

headless

label

2026-07-10 23:32:21 +00:00

coilyco-ops commented

2026-07-16 00:49:09 +00:00

Owner

Backlog consolidation on 2026-07-15: the agent is closing this P4 item as a reversible icebox entry. The work remains intentionally parked rather than completed. Kai can reopen it if she promotes it back into active direction.

coilyco-ops

2026-07-16 00:49:10 +00:00

closed this issue
removed the
autonomy
async-consult
label

No milestone

No project

No assignees

2 participants

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#171

No description provided.

Rows
Columns