From 0b306a7289f89f5237a0fc91c322c74f78c0bc08 Mon Sep 17 00:00:00 2001 From: Rachel Elledge Date: Wed, 16 Apr 2025 13:28:56 -0500 Subject: [PATCH] DOC-5105 RS: Removed outdated known limitation for updating syncer certificates --- .../operate/rs/security/certificates/updating-certificates.md | 1 - 1 file changed, 1 deletion(-) diff --git a/content/operate/rs/security/certificates/updating-certificates.md b/content/operate/rs/security/certificates/updating-certificates.md index f198b6c0b4..ffab97a185 100644 --- a/content/operate/rs/security/certificates/updating-certificates.md +++ b/content/operate/rs/security/certificates/updating-certificates.md @@ -140,5 +140,4 @@ To update your syncer certificate on clusters running Active-Active databases, f {{}} - Run step 2 as quickly as possible after step 1. Between the two steps, new syncer connections that use the ‘old’ certificate will get rejected by the cluster that has been updated with the new certificate (in step 1).
- Do not run any other `crdb-cli crdb update` operations between the two steps.
-- **Known limitation**: Updating syncer certificate on versions prior to 6.0.20-81 will restart the proxy and syncer connections. In these cases, we recommend scheduling certificate replacement carefully to minimize customer impact. {{}}