From the docs, 6.2. (Copying SSH keys) shows how to copy to multiple hosts via multiple networks. However this can be confusing as this is a single node cluster, so separate storage/management networks are not required. It's also confusing that there are examples for multiple nodes (this is for single node deployment). Chapter 2 mentions in the requirements: * 1 Network Interface Controller So I'm assuming environments with a single network are permitted. What I'd like to see is: * Chapter 2 - clarify that, while multiple networks are recommended/supported, only one is needed. * Chapter 6.2 - remove the examples for multiple nodes, add reminder (note) that multiple networks are recommended/supported, but not a hard requirement. https://access.redhat.com/documentation/en-us/red_hat_hyperconverged_infrastructure_for_virtualization/1.8/html/deploying_red_hat_hyperconverged_infrastructure_for_virtualization_on_a_single_node/task-configure-key-based-ssh-auth-single-node#generating-ssh-key-pairs-without-password
(In reply to Marcus West from comment #0) > From the docs, 6.2. (Copying SSH keys) shows how to copy to multiple hosts > via multiple networks. However this can be confusing as this is a single > node cluster, so separate storage/management networks are not required. > It's also confusing that there are examples for multiple nodes (this is for > single node deployment). > > Chapter 2 mentions in the requirements: > > * 1 Network Interface Controller > > So I'm assuming environments with a single network are permitted. > > What I'd like to see is: > > * Chapter 2 - clarify that, while multiple networks are > recommended/supported, only one is needed. > * Chapter 6.2 - remove the examples for multiple nodes, add reminder (note) > that multiple networks are recommended/supported, but not a hard requirement. > > > https://access.redhat.com/documentation/en-us/ > red_hat_hyperconverged_infrastructure_for_virtualization/1.8/html/ > deploying_red_hat_hyperconverged_infrastructure_for_virtualization_on_a_singl > e_node/task-configure-key-based-ssh-auth-single-node#generating-ssh-key- > pairs-without-password Hello Marcus, Thanks for the bug. Chapter 2 clearly states that 'requires': 1 network interface controller For single node RHHI-V deployment, single network is sufficient and required. There is no recommendation to make use of 2 networks for single node deployment. The changes in chapter 6.2 makes sense, and I will suggest the technical writer for those changes.
Verified with the internal doc link. Chapter 6.2 now has updated content to copy ssh public key from the node to itself. The irrelevant copy to host2 and host3 are now removed
The document is fixed and published