Issue in Chapter 4 - Building K8s clusters with Ansible about ansible-for-kubernetes HOT 3 CLOSED

@benheu - That is very strange—the only major difference I can see is you're using Vagrant 2.2.6 (2.2.7 is latest) and VirtualBox 6.0.18 (6.1.6 is latest). Maybe there's a difference there?

If it works with the config in ~/.ssh/config it seems that's the same as what ansible was trying to use via Vagrant...

from ansible-for-kubernetes.

Interesting, in researching this further I was brought to an issue on a different project I maintain: geerlingguy/drupal-vm#70

In it, someone mentioned IdentitiesOnly yes was the fix for them, too. It seems like this is a problem that may affect you if you use ssh identities and have more than 5 keys loaded via ssh-add!

By specifying the key in your ~/.ssh/config file directly, it offers that key first (no matter how many identities you have in your active ssh agent), and then authentication works.

Check how many keys are active with ssh-add -l and see if there are five or more.

Closing this issue as I believe that's the reason behind this and the fix, but thanks for posting your experience, hopefully to the benefit of future people who might Google the same issue!

from ansible-for-kubernetes.

Nice catch! Indeed I have 5 of them, thanks for taking the time looking into that.

from ansible-for-kubernetes.