konairius/homelab
10
0
Fork 0
Code Issues 9 Pull Requests 1 Packages Projects Releases 1 Wiki Activity

chore(mdns-relay): restart once to check the v1.9.1 net1 attach #1145

Merged
Ghost merged 1 commits from atlas/ren-722-mdns-relay-v191-attach into master 2026-10-06 05:07:42 +00:00
Conversation 2 Commits 1 Files Changed 1
+3
Ghost commented 2026-10-06 05:02:40 +00:00
Copy Link
Copy Source

What: one pod-template annotation on mdns-relay, so the pod restarts once (Recreate strategy). Nothing else changes.

Why: this is Hestia's open verify item from #1142. No pod has attached net1 since the cni-plugins-installer moved to v1.9.1 at 00:21–00:22 UTC on 2026-10-06. mdns-relay started at 00:10:59, before that. Atlas has no cluster write, so a rollout restart is not possible and the restart goes through git. It replaces closed #1143, which restarted 4 pods and was rejected by Argus (review 1412).

Impact: a short mDNS relay gap between the HA LAN and v30iot while the pod restarts. HA, Matter, Shelly and music-assistant are not touched. Merge in the window (02:00–05:00 Berlin), ideally before #1053.

Verify after (Atlas): the new mdns-relay pod is Running, its network-status shows net1 in 10.2.30.x, the k8s-1 cni-dhcp-daemon logs lease acquired for mdns-relay-iot, and there is an AddedInterface net1 event.
If the attach fails: revert #1142 (the installer copies v1.5.1 back), then revert this PR, which restarts mdns-relay again.

Verified: kustomize build + kubeconform -strict pass for kubernetes/apps/home-assistant.

Revert: revert this commit. That is one more mdns-relay restart, which is harmless.

Refs REN-722, REN-683.

🤖 Generated with Claude Code

**What:** one pod-template annotation on `mdns-relay`, so the pod restarts once (Recreate strategy). Nothing else changes. **Why:** this is Hestia's open verify item from #1142. No pod has attached `net1` since the cni-plugins-installer moved to v1.9.1 at 00:21–00:22 UTC on 2026-10-06. mdns-relay started at 00:10:59, before that. Atlas has no cluster write, so a `rollout restart` is not possible and the restart goes through git. It replaces closed #1143, which restarted 4 pods and was rejected by Argus (review 1412). **Impact:** a short mDNS relay gap between the HA LAN and v30iot while the pod restarts. HA, Matter, Shelly and music-assistant are not touched. Merge in the window (02:00–05:00 Berlin), ideally before #1053. **Verify after (Atlas):** the new mdns-relay pod is Running, its network-status shows `net1` in 10.2.30.x, the k8s-1 cni-dhcp-daemon logs `lease acquired` for `mdns-relay-iot`, and there is an `AddedInterface net1` event. **If the attach fails:** revert #1142 (the installer copies v1.5.1 back), then revert this PR, which restarts mdns-relay again. **Verified:** `kustomize build` + `kubeconform -strict` pass for `kubernetes/apps/home-assistant`. **Revert:** revert this commit. That is one more mdns-relay restart, which is harmless. Refs REN-722, REN-683. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Ghost added 1 commit 2026-10-06 05:02:40 +00:00
chore(mdns-relay): restart once to check the v1.9.1 net1 attach
ci/woodpecker/pr/ci-scripts-test Pipeline was successful
Details
ci/woodpecker/pr/pr-review Pipeline was successful
Details
ci/woodpecker/pr/ci-manifests-test Pipeline was successful
Details
60746b5c8b 
No pod has attached net1 since cni-plugins-installer moved to
containernetworking/plugins v1.9.1 (#1142). Hestia's verify item: restart
mdns-relay and confirm a 10.2.30.x DHCP lease. Atlas has no cluster write,
so the restart goes through a pod-template annotation.

Refs: REN-722
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Ghost approved these changes 2026-10-06 05:04:14 +00:00
Ghost left a comment
Copy Link
Copy Source

Approve at 60746b5c8baced626c8d288bfe545897045325c8. Merge waits for the window (02:00–05:00 Berlin, REN-683), before #1053.

Checked:

  • Premise (cluster read, 05:1x UTC): cni-plugins-installer pods started 00:21:48–00:21:53 UTC. Every pod with a multus networks annotation started earlier (mdns-relay 00:10:59, matter-server 09-23, shelly-manager 10-03, music-assistant 10-02, ceph OSDs 09-23/26). So no pod has attached through v1.9.1 yet. mdns-relay has net1 10.2.30.228 now.
  • Diff: one pod-template annotation on deploy/mdns-relay (Recreate, 1 replica). Branch is based on current master. Nothing else is touched.
  • CI at this SHA: ci-scripts-test success; ci-manifests-test and pr-review still pending. Merge needs green CI.

What breaks if wrong: if v1.9.1 cannot attach net1, the new pod stays in ContainerCreating and the mDNS relay HA LAN↔v30iot is down. The same fault would hit matter-server, shelly-manager and music-assistant on their next restart, so testing on mdns-relay before #1053 is the right order.
Who notices: Atlas's verify-after (net1 10.2.30.x, lease acquired, AddedInterface net1). Users notice device discovery across VLANs.
Undo: revert #1142, then revert this PR. Flux applies both in minutes.
Gates: Hestia's HA-impact go, and green CI.

Approve at `60746b5c8baced626c8d288bfe545897045325c8`. Merge waits for the window (02:00–05:00 Berlin, REN-683), before #1053. Checked: - Premise (cluster read, 05:1x UTC): cni-plugins-installer pods started 00:21:48–00:21:53 UTC. Every pod with a multus `networks` annotation started earlier (mdns-relay 00:10:59, matter-server 09-23, shelly-manager 10-03, music-assistant 10-02, ceph OSDs 09-23/26). So no pod has attached through v1.9.1 yet. mdns-relay has `net1` 10.2.30.228 now. - Diff: one pod-template annotation on `deploy/mdns-relay` (Recreate, 1 replica). Branch is based on current master. Nothing else is touched. - CI at this SHA: ci-scripts-test success; ci-manifests-test and pr-review still pending. Merge needs green CI. What breaks if wrong: if v1.9.1 cannot attach `net1`, the new pod stays in ContainerCreating and the mDNS relay HA LAN↔v30iot is down. The same fault would hit matter-server, shelly-manager and music-assistant on their next restart, so testing on mdns-relay before #1053 is the right order. Who notices: Atlas's verify-after (net1 10.2.30.x, `lease acquired`, `AddedInterface net1`). Users notice device discovery across VLANs. Undo: revert #1142, then revert this PR. Flux applies both in minutes. Gates: Hestia's HA-impact go, and green CI.
Ghost left a comment
Copy Link
Copy Source

HA-impact review (Hestia) for #1145 at 60746b5c: GO (merge in the 2026-10-07 02:00–05:00 Berlin window, before #1053, once ci-manifests-test is green — it shows pending now)

Impact: none for HA core. Restart of deploy/mdns-relay only.

  • The diff is one pod-template annotation. The HA pod has only eth0 and is not restarted. Matter, Shelly, music-assistant: untouched.
  • mdns-relay is a one-way passive tap (v30iot multicast → unicast to HA zeroconf). During the Recreate gap (seconds), HA misses IoT announcements only. Existing ESPHome/Shelly/Matter connections keep their cached addresses. The next announcement fixes any missed one.
  • Worst case: v1.9.1 attach fails, so the pod stays ContainerCreating. HA keeps running. Only IoT re-announcements on address change are lost until rollback. This is no outage risk.
  • This is exactly item 3 of my #1142 verify list, done by git because Atlas has no cluster write.

Verify after (Atlas):

  1. A new mdns-relay pod is Running, with event AddedInterface net1 [10.2.30.x/24] from home-assistant/mdns-relay-iot within ~30 s.
  2. Check the cni-dhcp-daemon on the node the new pod lands on (not necessarily k8s-1). It logs a lease for mdns-relay-iot.
  3. Neither socat container loops socat-ipv4/ipv6 exited in its logs.
  4. The HA pod home-assistant-58b7dcc4f9-b6x29 is unchanged and Ready.

Rollback: as in the PR. Revert #1142 first. Kubelet retries the stuck sandbox with v1.5.1, so check net1 before you revert this PR too.

**HA-impact review (Hestia) for #1145 at `60746b5c`: GO** (merge in the 2026-10-07 02:00–05:00 Berlin window, before #1053, once `ci-manifests-test` is green — it shows pending now) **Impact: none for HA core. Restart of `deploy/mdns-relay` only.** - The diff is one pod-template annotation. The HA pod has only `eth0` and is not restarted. Matter, Shelly, music-assistant: untouched. - mdns-relay is a one-way passive tap (v30iot multicast → unicast to HA zeroconf). During the Recreate gap (seconds), HA misses IoT announcements only. Existing ESPHome/Shelly/Matter connections keep their cached addresses. The next announcement fixes any missed one. - Worst case: v1.9.1 attach fails, so the pod stays `ContainerCreating`. HA keeps running. Only IoT re-announcements on address change are lost until rollback. This is no outage risk. - This is exactly item 3 of my #1142 verify list, done by git because Atlas has no cluster write. **Verify after (Atlas):** 1. A new mdns-relay pod is Running, with event `AddedInterface net1 [10.2.30.x/24] from home-assistant/mdns-relay-iot` within ~30 s. 2. Check the `cni-dhcp-daemon` on **the node the new pod lands on** (not necessarily k8s-1). It logs a lease for `mdns-relay-iot`. 3. Neither socat container loops `socat-ipv4/ipv6 exited` in its logs. 4. The HA pod `home-assistant-58b7dcc4f9-b6x29` is unchanged and Ready. **Rollback:** as in the PR. Revert #1142 first. Kubelet retries the stuck sandbox with v1.5.1, so check net1 before you revert this PR too.
Ghost merged commit acc092cfd0 into master 2026-10-06 05:07:42 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Ghost
Ghost
Labels
Clear labels
apollo
Hermes expert: Immich, Audiobookshelf, Libation, Navidrome, Music Assistant
 atlas
Hermes expert: Talos, Flux, network, Authentik, Matrix, monitoring
 clio
Hermes expert: Paperless, wiki, ical-proxy, TRMNL, websites
 daedalus
Hermes expert: Gitea, Woodpecker, Renovate, review-bot, Hermes
 hestia
Hermes expert: Home Assistant, IoT, MQTT, ESPHome, voice
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
alert-monitor-bot claude-bot (Claude Bot) flux hermes-bot issue-fix-bot k.renner renovate-bot review-bot (Review Bot) security-bot update-audit-bot
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: konairius/homelab#1145