-
Notifications
You must be signed in to change notification settings - Fork 549
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve catch-all network interface deviceSelector
.
#8090
Conversation
Signed-off-by: Markus Reiter <me@reitermark.us>
Nevermind, it seems these fields are not supported in the What is the recommended way to match the network interface on Raspberry Pis? It seems the only options are to match the driver ( |
Are you looking for a |
For my simple setup with only a single hardware interface per device, ideally I would not have to specify any selector and Talos should just use the only available interface. |
you can also use |
Closes siderolabs#8090 Signed-off-by: Andrey Smirnov <andrey.smirnov@siderolabs.com>
Closes siderolabs#8090 Signed-off-by: Andrey Smirnov <andrey.smirnov@siderolabs.com>
#8173 implements |
Closes siderolabs#8090 Signed-off-by: Andrey Smirnov <andrey.smirnov@siderolabs.com>
Pull Request
What? (description)
Change example for catch-all network interface
deviceSelector
.Why? (reasoning)
The existing example does not work on Raspberry Pi, I assume since the network interface is not a PCIe device but connected to the USB controller.
I am using Raspberry Pis (Hardware PHY) and Proxmox VMs (VirtIO PHY). The common attributes of the ethernet interfaces seem to be
type: ether
andkind: ''
.Acceptance
Please use the following checklist:
make conformance
)make fmt
)make lint
)make docs
)make unit-tests
)