Andrey Smirnov
Andrey Smirnov
Another idea: use "labels" (not Kubernetes Node labels, but Talos cluster member labels) to target nodes: ``` talosctl --label=controlplane bootstrap ```
## talosctl get `talosctl get members` shouldn't require a node as well, as this is cluster-wide resource. We could mark such resources in ResourceDefinition as cluster-wide and make `talosctl` use...
@Sonlis one way to debug the issue as we're flying in "blind" mode until `apid` is running (to make `talosctl logs` work) is to enable `debug` flag in the config...
Interesting point if that is something with interactive installer
This sounds like a bug, we probably forgot to update this place in the code while doing other a refactoring.
I guess the question I still have is what exactly to publish: * ISO * vmlinuz + initramfs (like PXE booting) * disk image How should actually Talos node on...
I think `nocloud` is kind of overcomplicated to work with, as it also covers networking configuration. It's not documented properly, but Talos can pick up machine config in `meta`l mode...
See also https://github.com/siderolabs/capi-utils/blob/master/pkg/capi/check.go#L32
(test it by deploying Rook cluster to QEMU with --extra-disks)