You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I remove the entry from known_hosts and try k0sctl again, it connects fine and I see this new entry in known_hosts (10.1.3.14 corresponds with the hostname):
If I use openSSH rather than ssh I don't have this issue, however it is much slower that way. It would be nice not to have to call out to openssh.
Last time I had a similar issue the problem was in the rig library. I mean no disrespect to the maintainers of rig, but I wonder if it's not yet mature enough for use in k0sctl?
The text was updated successfully, but these errors were encountered:
I'm having an issue where k0sctl and openssh seem to add conflicting entries to
~/.ssh/known_hosts
for the same host.I first connect to the hostname
bne-nxt1-vr-1
using openssh. It connects OK and I see this entry appear in known_hosts:if I then run k0sctl against the same hostname (using builtin
ssh
notopenSSH
config), I get an error:If I remove the entry from known_hosts and try k0sctl again, it connects fine and I see this new entry in known_hosts (10.1.3.14 corresponds with the hostname):
Additionally, I noticed k0sctl is adding the same entry to known_hosts repeatedly for this host (and others) e.g.
I'm using k0sctl v0.21.0 on MacOS 15.1.1
If I use
openSSH
rather thanssh
I don't have this issue, however it is much slower that way. It would be nice not to have to call out to openssh.Last time I had a similar issue the problem was in the rig library. I mean no disrespect to the maintainers of rig, but I wonder if it's not yet mature enough for use in k0sctl?
The text was updated successfully, but these errors were encountered: