This message was deleted.

I am wondering which idea stands behind loading the key from a webserver?

I think this is just a popular way of having SSH keys easily available during installation. For example, if you're a heavy GitHub user, your public SSH keys are served automatically at https://github.com/<YOURUSERNAME>.keys

Is it required to have the key located there permanently?

I don't believe so

Shall this mechanism allow to add are change public keys dynamically throughout the lifetime of harvester?

No, but here's the doc on how to change it after the fact: https://docs.harvesterhci.io/v1.2/install/update-harvester-configuration/#ssh-keys-of-user-rancher

Or is the key file only loaded once during installation?

Just during installation as far as I know.

I would also be interested in which format the file needs to be.

Just like any ssh authorized_keys file. One public key per line

Hello Connor, thanks for your help. Than my assumption was correct. Would indeed be good if one could simple pass in the public key rather than preparing anything in the web