assistant-api-ws: pin to enschede-t1000-1 to survive desktop power-off#596
Merged
Conversation
The rx7900xtx and gtx-960m Enschede nodes are desktops that are powered off periodically. When the pod lands on one of those nodes and the node goes offline, the k8s Service endpoint keeps pointing at the dead pod for the full node eviction window (~5 min), leaving the assistant WS completely broken. The fix pins the deployment to enschede-t1000-1, which is an always-on server node.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The assistant-api-ws deployment had no node affinity beyond
site=enschede + arch=amd64, so the scheduler could place the pod on the rx7900xtx or gtx-960m desktop nodes. Both are powered off when not in use. When a desktop goes offline, the k8s Service endpoint keeps pointing at the dead pod for the full node eviction window (~5 min), leaving the assistant WebSocket completely unavailable and Gatus going red.Today's incident:
enschede-rx7900xtx-1went NotReady at 16:38 UTC. The assistant-api-ws pod was on that node and stuck in Terminating. A new pod was eventually scheduled onenschede-t1000-1, but the terminal WS was dead for ~13 minutes.The fix pins the deployment to
enschede-t1000-1viapersonal-stack/node: enschede-t1000-1. That node is the always-on NAS/utility server (AdGuard, Samba, backup store) — it is never powered off. Thesite=enschedeandarch=amd64selectors are dropped as redundant once the node pin is in place.Immediate action required: force-delete the stuck Terminating pod on the offline node so the Service endpoint is clean: