Hi all, I was reading about some updates and I just wanted to confirm what I think I understand. I can install k3os from iso onto baremetal. I am prompted during the process including making a token if i want. Then, i can go to another baremetal machine and make it an agent and type in the token, ip address and it will work? I dont have to call up a github url if i dont want to during the install?

this sounds correct to me

How can I ssh remotely to a k3os instance?

have a valid public key in the

ssh_authorized_keys: []

array and/or set a password via

k3os.password

(yaml

k3os: {password: "", ...}

so it would be easier to set a password at the command line

if you didnt do that when you provisioned it, you can hit

e

in the grub menu and add

k3os.password=mypassword

on the kernel command line as a one-time override (the password will be forgotten next boot, so update your config)

how do i get to supply public ssh keys. these machines are physical, not virtual

how are you getting the config to them?

thats why im posting here for help!

i see. well, what i tend to do with homelab boxes is: • boot to "live" mode via installation media while supplying a

k3os.password

value on the kernel command-line •

ssh rancher@<host>

using said password to verify connectivity • copy over the

config.yaml

via the ssh connectivity. for me this is usually

scp

can i also set a file to bring in via github??

i don't believe so. the config.yaml is a one-shot at install time iirc