Helper name resolution config always adds FQDN about ocp4-helpernode

[canit00]

Hi David -

Being able to ssh to any node in the cluster is logically done for user convenience & also taking into account that users may be working in environments with different environmental configurations, etc..

That being said, the code snippet creates an ssh key pair specifically for the cluster which configures your $HOME/.ssh/config with the FQDN provided in the vars.yaml file along with the core user as it's default in RHCOS.

https://github.com/RedHatOfficial/ocp4-helpernode/blob/master/tasks/generate_ssh_keys.yaml#L1-L23

Sorry if this caused confusion.

[bassplay3r]

But I provided my public key in the install-config.yaml and the helper_rsa is not my private key
Did I miss a step?
I don't mind telling my users to do ssh worker0 if the key works

[root@helper ~]# ssh worker0
Permission denied (publickey,gssapi-keyex,gssapi-with-mic).
[root@helper ~]#

It works when I do ssh -i mykey core@worker0

[christianh814]

But I provided my public key in the install-config.yaml and the helper_rsa is not my private key
Did I miss a step?
I don't mind telling my users to do ssh worker0 if the key works

[root@helper ~]# ssh worker0
Permission denied (publickey,gssapi-keyex,gssapi-with-mic).
[root@helper ~]#

It works when I do ssh -i mykey core@worker0

Look in ~/.ssh/config and all will be answered.

As @canit00 eluded, it defaults to use the key it auto generates https://github.com/RedHatOfficial/ocp4-helpernode/blob/master/tasks/generate_ssh_keys.yaml#L1-L23

If you look at the vars doc you'll see you can turn off creating an ssh-key by setting ssh_gen_key: false in your vars.yaml file.

[bassplay3r]

Thanks for extra info, it's been a long day. I'll probably have to disable the feature. I looked on the worker and all of the authorized_keys files match the public key I provided. I tried renaming my private key file helper_rsa and giving it the same perms and that does not work.

You might want to add some more info after this line in the quickstart for those providing their own key to disable the keygen:
This playbook creates an sshkey for you; it's under ~/.ssh/helper_rsa. You can use this key or create/user another one if you wish.

[christianh814]

Thanks for extra info, it's been a long day. I'll probably have to disable the feature. I looked on the worker and all of the authorized_keys files match the public key I provided. I tried renaming my private key file helper_rsa and giving it the same perms and that does not work.

You might want to add some more info after this line in the quickstart for those providing their own key to disable the keygen:
This playbook creates an sshkey for you; it's under ~/.ssh/helper_rsa. You can use this key or create/user another one if you wish.

Good idea. Added a note on commit 1058934

This will make it's way into master next release (sometime next week)