k3s-config stage is coupled to unavailable Traefik first-provision input #678

Open
opened 2026-07-28 23:43:41 +00:00 by coilyco-ops · 0 comments
Owner

Running the non-disruptive k3s-config-stage path on kai-server successfully installed the safe systemd configuration and skipped the k3s restart, but the play then failed in the Traefik block.

Observed failure:

The Traefik load-balancer address could not be resolved from /coilysiren/home/public-ip, and no existing config can be preserved.

The core stage operation should be able to complete without requiring an unrelated Traefik render. The first-provisioning Traefik path must still fail closed when an operator actually requests it.

Acceptance:

  • tags=k3s-config-stage completes after installing and daemon-reloading the k3s systemd files, without restarting k3s.
  • An unavailable Traefik input does not fail the core stage path.
  • An explicit first-time Traefik provision still requires the SSM-backed address and fails closed when unavailable.
  • The role reports which independent component was skipped without exposing the address.
Running the non-disruptive `k3s-config-stage` path on kai-server successfully installed the safe systemd configuration and skipped the k3s restart, but the play then failed in the Traefik block. Observed failure: ```text The Traefik load-balancer address could not be resolved from /coilysiren/home/public-ip, and no existing config can be preserved. ``` The core stage operation should be able to complete without requiring an unrelated Traefik render. The first-provisioning Traefik path must still fail closed when an operator actually requests it. Acceptance: * `tags=k3s-config-stage` completes after installing and daemon-reloading the k3s systemd files, without restarting k3s. * An unavailable Traefik input does not fail the core stage path. * An explicit first-time Traefik provision still requires the SSM-backed address and fails closed when unavailable. * The role reports which independent component was skipped without exposing the address.
Sign in to join this conversation.
No project
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#678
No description provided.