diff --git a/content/en/containers/guide/kubernetes-cluster-name-detection.md b/content/en/containers/guide/kubernetes-cluster-name-detection.md
index 8a3aad2eebf..02e11837852 100644
--- a/content/en/containers/guide/kubernetes-cluster-name-detection.md
+++ b/content/en/containers/guide/kubernetes-cluster-name-detection.md
@@ -21,10 +21,10 @@ For Agent v6.11+, the Datadog Agent can automatically detect the Kubernetes clus
 <div class="alert alert-info">
 This cluster name should be a unique name and abide by the following restrictions:
 <ul>
-  <li/>Must only contain lowercase letters, numbers, and hyphens
-  <li/>Must start with a letter
-  <li/>Must end with a number or a letter
-  <li/>Must be less than or equal to 80 characters
+  <li/>Must contain only lowercase letters, numbers, dots, hyphens, and underscores
+  <li/>Must start with an alphanumeric character
+  <li/>Must end with an alphanumeric character
+  <li/>Must be similar to a Fully Qualified Domain Name (FQDN), without a trailing period
 </ul>
 </div>
 
@@ -117,4 +117,4 @@ If the node label is found, the value is used as the cluster name.
 [2]: https://learn.microsoft.com/en-us/azure/virtual-machines/instance-metadata-service?tabs=linux
 [3]: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instancedata-data-retrieval.html
 [4]: https://docs.aws.amazon.com/eks/latest/userguide/pod-id-how-it-works.html
-[5]: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/work-with-tags-in-IMDS.html#allow-access-to-tags-in-IMDS
\ No newline at end of file
+[5]: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/work-with-tags-in-IMDS.html#allow-access-to-tags-in-IMDS