Expected Behaviour

k3sup is usable for users who do not use files for private key auth. Smart cards for example.

Current Behaviour

Tool fails due to no private key file existing on the filesystem.

Possible Solution

Silently attempt to establish the SSH connection before falling back to the existing file based auth. This allows users with smart cards, or who have pre-configured ssh-agents to work. If not using a smart card the end user will see no change to existing behaviour.

Fixes #255

Steps to Reproduce (for bugs)

1. Yubikey with no private key file on disk
2. Use install command
3. Fails with unable to load the ssh key with path...

Context

Had tried using k3sup to setup k3s as a replacement for my old k8s cluster, doesn't support my use of a Yubikey for SSH auth.

Your Environment

• What Kubernetes distribution are you using?

n/a

• What OS or type or VM are you using for your cluster? Where is it hosted? (for k3sup install/join):

Ubuntu 20.04 on a NUC.

• Operating System and version (e.g. Linux, Windows, MacOS):

OSX 10.15.7

"Be part of the solution"

Subject to approval, are you willing to work on a Pull Request for this issue or feature request?

Yes, I have it working on a fork already.