Documentation : Replicate SSL keys between geo primary and secondaries
When using HTTPS, after failing over to a secondary and updating DNS records, the new primary will not be accessible via HTTPS because the SSL keys won't match.
We should include instructions to replicate SSL keys across all geo secondaries.
Scenario
The primary is at https://one.geo.gitlab.example.com/ and the secondary at https://two.geo.gitlab.example.com/. When the primary goes down and the secondary is promoted to primary, the instructions include an (optional) step to change the DNS name for the promoted secondary to https://one.geo.gitlab.example.com. But that host, still serves the SSL certificates for https://two.geo.gitlab.example.com. So users browsing to that promoted secondary get an error indicating the SSL connection is not secure.
Implementation Guide
Update this step in our documentation to say "Update the SSL certificate if necessary".