diff --git a/kb/2024-05-17/imgs/cc-renew.png b/kb/2024-05-17/imgs/cc-renew.png
new file mode 100644
index 00000000..dcac9744
Binary files /dev/null and b/kb/2024-05-17/imgs/cc-renew.png differ
diff --git a/kb/2024-05-17/modify_cloud_credential_ttl.md b/kb/2024-05-17/modify_cloud_credential_ttl.md
index 09c2cc60..1afcbf68 100644
--- a/kb/2024-05-17/modify_cloud_credential_ttl.md
+++ b/kb/2024-05-17/modify_cloud_credential_ttl.md
@@ -61,3 +61,13 @@ You can patch the expired Harvester cloud credentials to use a new authenticatio
   :::info important
   macOS users must use `gbase64` to ensure that the `-w` flag is supported.
   :::
+
+## Expiration of kubeconfig Tokens in Rancher 2.9.3
+
+In Rancher 2.9.3 and later versions, the Rancher UI displays a warning when a Harvester cloud credential or a related cluster contains an expired token. You can renew the token on the **Cloud Credentials** screen by selecting **⋮ > Renew**, or the Clusters screen by selecting **⋮ > Renew Cloud Credential**
+
+![cc-renew](./imgs/cc-renew.png)
+
+:::note
+When you upgrade Rancher, the Rancher UI does not display a warning for Harvester cloud credentials that expired before the upgrade was started. However, you can still renew the token on the **Cloud Credentials** or **Clusters** screen.
+:::
\ No newline at end of file