feat(talos): add justfile tooling and fix CP-1 network selector#62
Merged
feat(talos): add justfile tooling and fix CP-1 network selector#62
Conversation
- Add justfile with recipes for common Talos operations: - genconfig: Generate machine configs via talhelper - bootstrap: Initialize first control plane node - kubeconfig: Fetch cluster credentials - dashboard: Open talosctl dashboard - status/services/logs: Node inspection commands - apply-config: Apply config updates to nodes - Flexible node targeting (cp-1, cp-2, cp-3, or all) - Fix CP-1 network interface selector: - Change from wildcard (*) to specific MAC address (38:05:25:34:25:d0) - Wildcard was matching multiple interfaces (bond0, dummy0, enp2s0) - This caused VLAN interfaces on wrong devices and gateway route issues - Add .gitignore for generated clusterconfig/ directory 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Bridge eth1.30 (switch trunk) and eth2.30 (UM760 direct connect) to allow the UM760 platform anchor node to participate in VLAN 30 without requiring the traffic to traverse the switch. - Add br30 bridge with gateway IP 10.10.30.1/24 - Move IP from eth1.30 to br30 (eth1.30 now bridge member) - Add eth2.30 VLAN interface as bridge member - Update documentation with bridge architecture 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
The platform network (VLAN 30) now uses a bridge (br30) to allow the UM760 anchor node to participate via a direct connection. Update the operational tests to reflect this: - Remove VLAN 30 from parametrized test_vlan_interface_up - Add dedicated test_vlan30_bridge_interface_up that validates: - VLAN interface is up and is a bridge member - Bridge br30 is up with the gateway IP 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.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
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.
Summary
*to specific MAC addressProblem
The wildcard
hardwareAddr: "*"in talconfig.yaml was matching multiple interfaces (bond0, dummy0, enp2s0), causing Talos to create VLAN 30 sub-interfaces on all of them. This confused Talos's network stack - it couldn't determine which interface should be primary, so the gateway route wasn't applied properly, resulting in no network connectivity.Solution
Changed to the specific MAC address (
38:05:25:34:25:d0) for the UM760's 2.5GbE port that connects to VyOS eth2.New Justfile Commands
just genconfigjust bootstrapjust kubeconfigjust dashboard [node]just status [node]just services [node]just logs <service> [node]just apply-config <node>just talosctl <args>Node targeting supports:
cp-1/cp1/1,cp-2/cp2/2,cp-3/cp3/3, orallTest plan
🤖 Generated with Claude Code