Document URL: 

https://access.redhat.com/documentation/en-us/red_hat_update_infrastructure/4/html/configuring_and_managing_red_hat_update_infrastructure/assembly_cmg-managing-content-delivery-servers

https://access.redhat.com/documentation/en-us/red_hat_update_infrastructure/4/html/configuring_and_managing_red_hat_update_infrastructure/assembly_cmg-managing-haproxy-load-balancer-instance

Section Number and Name: 

Chapter 6. Managing content delivery servers
Chapter 7. Managing an HAProxy load-balancer instance

Describe the issue: 

The descriptions in the chapters are not clear about whether a user should use .ssh/id_rsa or ~.ssh/id_rsa_rhua as the private key for configuring cds and haproxy.

6.1. Listing all known CDS instances managed by RHUI 4: .ssh/id_rsa is used in an example

6.2. Registering a new CDS: .ssh/id_rsa is used in an example of TUI input but .ssh/id_rsa_rhua is used in an example of CLI input.

6.3. Reinstalling and reapplying configuration to a CDS: .ssh/id_rsa_rhua is used in an example of TUI input.

7.1. Listing all known HAProxy load-balancer instances managed by RHUI 4: .ssh/id_rsa_rhua is used in an example.

7.2. Registering a new HAProxy load-balancer: .ssh/id_rsa is used in an example of TUI input.

7.3. Reinstalling and reapplying the configuration to an HAProxy load-balancer: ssh/id_rsa_rhua is used in an example of TUI input.


Suggestions for improvement: 

If there is a reason using both .ssh/id_rsa_rhua and .ssh/id_rsa, we should explain the reason clearly not to make users confused.

If there is no reason, use only .ssh/id_rsa_rhua. Making /root/.ssh/id_rsa_rhua as default value for `--keyfile_path` option of `rhui-manager haproxy add` and `rhui-manager cds add`

Additional information: 


None.