Description of problem:

Some users will have a server running Satellite with the name of "system123.example.com", but do not want to expose this system name externally for security or HA/DR reasons. Instead, they would like to point "satellite.example.com" to the same IP as "system123.example.com" (or use a load balancer for convenience), and have the satellite server present itself via is SSL certs as "satellite.example.com". They would also like to keep the server's actual hostname as "system123.example.com" to avoid confusion when doing maintenance.

As a workaround, users can run "hostnamectl set-hostname satellite.example.com" on the Satellite server, run the installer, then change the system's hostname back to "system123" again. If the user forgets to do this, the Satellite will get into a confused and broken state with its SSL certs.

This request is different than what satellite-change-hostname provides today. Satellite-change-hostname will change the system's fqdn in addition to certificates.

This request is also different than using custom certificates. These are typically only for https on port 443, but do not include qpidd/qdrouterd and other services.

One idea would be to add another installer flag that allows setting an arbitrary hostname for the Satellite that is not necessarily the FQDN of the system. Satellite-change-hostname may be able to handle this as well as a new feature, but I am not sure how it would persist the changes across runs of satellite-installer.

Version-Release number of selected component (if applicable): 6.3.1