Dimitris Karakasilis

The spegel pods fails with: ``` │ registry {"time":"2025-08-05T12:58:24.446611958Z","level":"INFO","source":{"function":"github.com/spegel-org/spegel/pkg/routing.bootstrapFunc.func1","file":"github.com/spegel-org/spegel/pkg/routing/p2p.go","li │ │ ne":348},"msg":"no bootstrap nodes found","logger":"p2p"} ``` probably due to: https://github.com/spegel-org/spegel/issues/709#issuecomment-2615412433

I created a PR to fix provider-kairos to respect the settings in the manual cluster case. With that, I was able to deploy a 2 node cluster and follow the...

I also see these lines in the worker k3s-agent.service journal logs: ``` Aug 06 10:44:38 metal-6cb1 k3s[1863]: time="2025-08-06T10:44:38Z" level=info msg="Using private registry config file at /etc/rancher/k3s/registries.yaml" ... Aug 06 10:44:38...

Cut a new kairos-init release with the fixes provider: https://github.com/kairos-io/kairos-init/releases/tag/v0.5.9 We need a new release of Kairos before we push the docs.

Tested with k0s and manual installation of spegel and it works fine there too!. Documented the process here: https://github.com/kairos-io/kairos-docs/pull/451/files I need to go through the docs PR and cleanup and...

I merged the PR since it goes into "dev" branch

@phillebaba we tested and documented the use of spegel with k3s and k0s but we wonder what the support is for kubeadm-created clusters. We don't see anything mentioned here: https://spegel.dev/docs/getting-started/#compatibility...

Created a new ticket to try on kubeadm: https://github.com/kairos-io/kairos/issues/3581

These: https://github.com/kairos-io/kairos-init?tab=readme-ov-file#building-args don't match this: ``` ~/workspace/kairos/kairos-init (main)*$ ./build/kairos-init --help Kairos init tool for system initialization and configuration Usage: kairos-init [flags] kairos-init [command] Available Commands: completion Generate the autocompletion script...

> Maybe we should have like a expert toggle around that shows stuff like this? So we use the whatever is in there by default but then let advanced users...