David Brouwer
David Brouwer
Yes but you don't want to write out 20 ENVs. I managed to solve it like this, but the stateful set is missing the `extraArgs` option ```yaml deployment: extraVolumes: -...
I was confused as in the same helm template, both `statefulSet` and `statefulset` were used. I changed all to the former since it aligns more with the rest of the...
I am having a similar issue, `talosctl` never gets past `waiting for API` with qemu. Qemu nodes refuse to communicate with each other. `10.5.0.1` pings perfectly fine but `10.5.0.2-5` don't....
@hobyte How did you get the log output from the qemu vms? My .log files only contain the startup command, and `talosctl --talosconfig talos-config -n 10.5.0.2 dmesg` failed to determine...
Mine only contain the setup command ``` ❯ tail -F talos-alderson-*.log ==> talos-alderson-master-1.log talos-alderson-worker-1.log
I think it's expected to happen in the beginning, before the cluster has bootstrapped, but after a few min the kubelets should be running and it should resolve.
Yeah I think so too. I moved on to playing with Talos on virtual private servers. Its distro related though, works fine on other distros
What you could try is to instead of using the qemu provisioner, manually create qemu-kvm's using the talos ISO
I tried that, only allowed me to use docker, not qemu. Does qemu fully work for you now?
Since this issue is mentioned in the Cilium docs, which parameters exactly are good to change for use with Cilium? I see the first 3 in the original issue have...