k3sup join needs two --ssh-key, one for server and another one for joining server about k3sup HOT 3 CLOSED

Hi @aminnasiri

We haven't needed this in three and a half years, so I think it's safe to say that we don't need it now.

In fact, there is a very simple fix here, which is for you to run ssh-copy-id user@server.

Regards,

Alex

from k3sup.

/add label: support, question,wontfix

from k3sup.

I tried these commands before creating this ticket and got an error too.
Steps:
ssh-copy-id -i ~/.ssh/<master-public.key>.pub opc@<master-server-ip>

k3sup join \
  --ip 129.146.72.24 \
  --user <new-server-user> \
  --sudo \
  --server-user <master-server-user> \
  --server-ip <master-server-ip> \
  --ssh-key ~/.ssh/<new-server-private.key>.key \
  --server 

The error

Error: unable to connect to<master-server-ip> over ssh as  <master-server-user>: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain

I don't know how you have been handling this situation, but there are lots of tickets on it in different ways of explanations on this git-repo.

from k3sup.