diff --git a/docs/troubleshooting/other-troubleshooting-tips/logging.md b/docs/troubleshooting/other-troubleshooting-tips/logging.md
index d4d6353442e..6d0e6dd9b4f 100644
--- a/docs/troubleshooting/other-troubleshooting-tips/logging.md
+++ b/docs/troubleshooting/other-troubleshooting-tips/logging.md
@@ -78,3 +78,19 @@ possible to enable debug logs in `rancher-machine` when provisioning RKE1, RKE2
 Just like the `trace` log level above, `rancher-machine` debug logs can contain sensitive information.
 
 :::
+
+
+## Cattle-cluster-agent debug logs
+
+The `cattle-cluster-agent` log levels can be set when you initialize downstream clusters.
+
+When you create a cluster under **Cluster Configuration > Agent Environment Vars** you can set variables to define the log level.
+- Trace-level logging: Set `CATTLE_TRACE` or `RANCHER_TRACE` to `true`
+
+- Debug-level logging: Set `CATTLE_DEBUG` or `RANCHER_DEUBG` to `true`
+
+:::caution
+
+The `cattle-cluster-agent` debug logs may contain sensitive information.
+
+:::
diff --git a/src/pages/versions.md b/src/pages/versions.md
index e30f1483b84..6cd8feaf4af 100644
--- a/src/pages/versions.md
+++ b/src/pages/versions.md
@@ -10,10 +10,10 @@ Below are the documentation and release notes for the currently released version
 
 <table>
   <tr>
-    <td><b>v2.7.6</b></td>
+    <td><b>v2.7.7</b></td>
     <td><a href="https://ranchermanager.docs.rancher.com/v2.7">Documentation</a></td>
-    <td><a href="https://github.com/rancher/rancher/releases/tag/v2.7.6">Release Notes</a></td>
-    <td><a href="https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/rancher-v2-7-6/">Support Matrix</a></td>
+    <td><a href="https://github.com/rancher/rancher/releases/tag/v2.7.7">Release Notes</a></td>
+    <td><a href="https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/rancher-v2-7-7/">Support Matrix</a></td>
   </tr>
 </table>
 
@@ -33,6 +33,12 @@ Below are the documentation and release notes for the currently released version
 Below are the documentation and release notes for previous versions of Rancher 2.7.x:
 
 <table>
+  <tr>
+    <td><b>v2.7.6</b></td>
+    <td><a href="https://ranchermanager.docs.rancher.com/v2.7">Documentation</a></td>
+    <td><a href="https://github.com/rancher/rancher/releases/tag/v2.7.6">Release Notes</a></td>
+    <td><a href="https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/rancher-v2-7-6/">Support Matrix</a></td>
+  </tr>
   <tr>
     <td><b>v2.7.5</b></td>
     <td><a href="https://ranchermanager.docs.rancher.com/v2.7">Documentation</a></td>
diff --git a/versioned_docs/version-2.7/troubleshooting/other-troubleshooting-tips/logging.md b/versioned_docs/version-2.7/troubleshooting/other-troubleshooting-tips/logging.md
index d4d6353442e..6d0e6dd9b4f 100644
--- a/versioned_docs/version-2.7/troubleshooting/other-troubleshooting-tips/logging.md
+++ b/versioned_docs/version-2.7/troubleshooting/other-troubleshooting-tips/logging.md
@@ -78,3 +78,19 @@ possible to enable debug logs in `rancher-machine` when provisioning RKE1, RKE2
 Just like the `trace` log level above, `rancher-machine` debug logs can contain sensitive information.
 
 :::
+
+
+## Cattle-cluster-agent debug logs
+
+The `cattle-cluster-agent` log levels can be set when you initialize downstream clusters.
+
+When you create a cluster under **Cluster Configuration > Agent Environment Vars** you can set variables to define the log level.
+- Trace-level logging: Set `CATTLE_TRACE` or `RANCHER_TRACE` to `true`
+
+- Debug-level logging: Set `CATTLE_DEBUG` or `RANCHER_DEUBG` to `true`
+
+:::caution
+
+The `cattle-cluster-agent` debug logs may contain sensitive information.
+
+:::