Repository navigation
bootstrap: pin the TOE Deployment to the k3s server node - #35
Merged
Merged
Conversation
TOE mounts hostPath /etc/teknoir and signs its MQTT JWT with the device keys in it. On a multi-node Robot the pod could land on a joined agent node, read that node's own keys and be refused by EMQX (reason 135). Add nodeSelector node-role.kubernetes.io/control-plane=true, which k3s sets on server nodes only. Goldens regenerated. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The ansible toe-image playbook recognises the pin only when nodeSelector is on the line directly after priorityClassName; the three comment lines between them made it report a conflict. Goldens regenerated. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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 TOE Deployment in the bootstrap manifest had no nodeSelector; on a robot with agent nodes TOE can be scheduled onto an agent, where /etc/teknoir holds that node's keys, and EMQX refuses it (staging orin, 2026-10-22). The template now pins TOE with `nodeSelector: node-role.kubernetes.io/control-plane: "true"` directly after `priorityClassName: high-priority-toe` (the position ansible toe-image.yml recognises). Single-node robots are unaffected. Goldens regenerated (+5 lines in server, docker_server, server.roles).
go test ./... in pkg/templates, go test ./cmd/..., go vet clean. Opus review.
🤖 Generated with Claude Code