This message was deleted.
# harvester
a
This message was deleted.
c
well you have
sshauthorizedkeys: []
and
ssh_authorized_keys:
- which one do you think is right?
isn’t ssh_authorized_keys a cloud-init
#cloud-config
thing? That only works in Harvester VMs, not for installing Harvester
t
I read that as harvester itself.
c
I suspect the docs are wrong? it also says os.write_files but you have os.writefiles
t
where do you see ``sshauthorizedkeys`` ?
can you fix the docs? lol
c
the use of snakes and camel case in this config syntax is really disturbing
t
what is your goto install yaml?
c
like, consistently do externalStorageConfig or external_storage_config but having that and some that are just all lowercase like rawdiskimagepath is just… terrible
t
lol
c
shows lack of any consistent design review
code says it is sshAuthorizedKeys, so if it is case insensitive I suspect sshauthorizedkeys will also work >
Copy code
SSHAuthorizedKeys          []string `json:"sshAuthorizedKeys,omitempty"`
and that is also what you have as an example at the top of your yaml so…
t
good eye. let me test.
c
Hit that
Edit this page
button at the bottom there
t
lol
Copy code
sshAuthorizedKeys
confirmed!
thanks!
c
I poked the harvester guys about it. They’re all APAC as I’m sure you know
t
i remember.. I added the others that were underscored.
looks like ALL of them with underscores are bad.. so fun!
m
@thousands-advantage-10804 not sure what it is, for new install,
ssh_authorized_keys
works for me... my config looks like this:
Copy code
scheme_version: 1
os:
  hostname: sand.isim.dev
  ssh_authorized_keys:
    - ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBNtRt9WeQJNVU9IXsqY8taNCdAeMEP8RRGU1QSFF7SD4aX21f1zQ5KmVTPYRllt95rh2RKpk3uRuiURBBej0d68= isim@pop-os
  ntpServers:
    - <http://0.suse.pool.ntp.org|0.suse.pool.ntp.org>
    - <http://1.suse.pool.ntp.org|1.suse.pool.ntp.org>
install:
  wipeAllDisks: true
(ignore the ugly, mixed case, i'm just changing some of them for testing)
👀 1
👍 1
t
Copy code
sshAuthorizedKeys
works.
c
I suspect it might have to do with the duplicate keys? Andy had it in there twice, in different formats.
t
might be.
a
my guess (without testing) is the duplicated keys
I have no idea of the exact history behind this, but our docs say to use underscores, while the harvester installer (when it writes out /oem/harvester.config later) doesn't. See also this rotten thing: https://github.com/harvester/harvester/issues/9290
🙃 1
harvester installer should at least be able to read both formats (with and without underscores), so it shouldn't matter whether you use ssh_authorized_keys or sshAuthorizedKeys
👍 1
b
Late to the party. We're using
ssh_authorized_keys
from the beginning (Harvester 1.0) and it worked. But we didn't redeploy a lot of nodes, so I wouldn't have noticed that it broke in the middle...