That’s a great question!
Octopus Server Configuration
When changing the URL, there will be a few things you need to consider. You will need to change or set up the DNS records for the new URL in preparation. For instance, if octopus.company.com is pointing to IP 220.127.116.11 and this isn’t changing, then you will need to point octopus-prd.company.com to the same IP. Your new DNS record will need to point to the load balancer.
The next step will be to bind the Hostname to your Octopus Instance for each node in your Highly-Available cluster, and you can do that in Octopus.Server.exe directly on the Octopus Server(s). When you are binding this, you need to also attach the SSL certificate directly to Octopus when configuring the new URL. Unless you are using a Wildcard Certificate then you will need to purchase an SSL certificate from a Certificate Authority or generate an Active Directory domain certificate for Octopus to use.
The next consideration is where it gets a little trickier, and this will be the Tentacle configuration. If you are using only Listening Tentacles, where the Octopus Server connects to the Tentacle, then no further configuration is required.
When using Polling Tentacles, where the Tentacle connects directly to the Octopus server, then you will need to configure these to point to the new URL. We have a page on our site which covers how to do this automatically, and this is on Automating Tentacle installation - Octopus Deploy.
We would recommend looking at Polling tentacles with HA - Octopus Deploy as if you choose to re-register your Polling tentacles, then you need to register it with each Octopus Server.
The reason you need re-register the tentacle is because the URL it will be trying to connect to will no longer be pointing to Octopus. A possible way to mitigate this would be to keep octopus.company.com as an alias, and that way, you won’t need to reconfigure the Polling Tentacles to the new URL.
Please let me know if you have any questions.