Score:0

Deploying k3os through a single image across all nodes with a shared token

no flag

I'm trying to get a k3os cluster running on a set of Raspberry Pi nodes using https://github.com/sgielen/picl-k3os-image-generator. I'm successfully generating images and I am able to boot from them. However, even though I have a token entry in each of my config files (token and secret replaced):

k3os:
  token: K10e8c37ea0000000000000000000000000000002cbdaef2f8d7bd2f5b6931b4f52b::server:secret

when the first node boots, it seems to generate a new secret for the cluster anyway, which means the other nodes can't join. I know I can pull out the new token from the cluster and rebuild the images, but I'd rather figure out how to have one image that I create once and use. I'm sure I'm missing something silly...

Score:0
no flag

it seems that k3os is dead

https://github.com/rancher/k3os/issues/846

and its replacement is basically dead

https://github.com/rancher/k3os/issues/846#issuecomment-1040252582

so I have decided just to give up and use a normal OS and normal management, because I don't have time to fight this any longer.

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.