Needs to be cloned to Part 4. Part 4 redundancy section describe a pool of hot redundant servers that can be accessed round robin by clients for load balancing. This works where the servers in the hot set all have certs from the same CA and its the CA that is trusted by the Clients (not the individual certs.);

Cloned from part 2 issue

I am not sure why any solution that adresses the original question would make sense for what the hostname/DNS name is in the certificate.

The DNS name in the certificate is used by the client to compare the hostname in the EndpointUrl used to connect with the certificate.
Does this DNS name of the server really change?
Are the intenal names used by clients to connect?

The containers can share the hostname, although it's not necessarily straight forward how to accomplish it (via a configuration file on the persistent volume - or the certificate - or an argument to the container if it's started manually from the Docker host).

They will need to share the connection address anyway, so that the clients can connect.

But, maybe it's a good idea to describe how the containerised applications should be configured.