diff --git a/website/content/docs/upgrading/upgrade-to-1.6.0.mdx b/website/content/docs/upgrading/upgrade-to-1.6.0.mdx
index 77782f680..acc515c77 100644
--- a/website/content/docs/upgrading/upgrade-to-1.6.0.mdx
+++ b/website/content/docs/upgrading/upgrade-to-1.6.0.mdx
@@ -45,5 +45,8 @@ more information on upgrading custom database plugins.
 ## Known Issues
 
 Due to the known issue, Transform Secrets Engine users are recommended to upgrade to version 1.6.4.
+Due to the known issue, Lease Count Quota users with DR Secondaries are recommended to upgrade to version 1.6.6.
 
 @include 'transform-upgrade.mdx'
+
+@include 'lease-count-quota-upgrade.mdx'
diff --git a/website/content/docs/upgrading/upgrade-to-1.7.0.mdx b/website/content/docs/upgrading/upgrade-to-1.7.0.mdx
index 15f8a1fc6..bee4adbe0 100644
--- a/website/content/docs/upgrading/upgrade-to-1.7.0.mdx
+++ b/website/content/docs/upgrading/upgrade-to-1.7.0.mdx
@@ -31,7 +31,8 @@ endpoint changes is available in the [AWS Auth API docs](/api-docs/auth/aws#depr
 
 ## Known Issues
 
-Due to the known issue, Transform Secrets Engine users are recommended to upgrade to version 1.6.4 or 1.7.0.
+Due to the known issue, Transform Secrets Engine users are recommended to upgrade to version 1.7.0.
+Due to the known issue, Lease Count Quota users with DR Secondaries are recommended to upgrade to version 1.7.4.
 
 ### Autopilot
 
@@ -43,3 +44,5 @@ Due to the known issue, Transform Secrets Engine users are recommended to upgrad
   `VAULT_RAFT_AUTOPILOT_DISABLE` environment variable to 1.
 
 @include 'transform-upgrade.mdx'
+
+@include 'lease-count-quota-upgrade.mdx'
diff --git a/website/content/partials/lease-count-quota-upgrade.mdx b/website/content/partials/lease-count-quota-upgrade.mdx
new file mode 100644
index 000000000..4e3b10380
--- /dev/null
+++ b/website/content/partials/lease-count-quota-upgrade.mdx
@@ -0,0 +1,5 @@
+### Lease Count Quota Invalidations on DR Secondaries Fixed
+
+Lease count quota invalidation causes DR Secondaries to panic and experience
+a hard shutdown. This issue exists prior to Vault 1.6.6 and 1.7.4. It is
+fixed in Vault 1.6.6, 1.7.4, and 1.8.0.