From ab9ae41af9c69002821b3350c52b863ef36e5883 Mon Sep 17 00:00:00 2001
From: Yohann Fabri <11197007+YoranSys@users.noreply.github.com>
Date: Tue, 1 Oct 2024 07:31:58 -0400
Subject: [PATCH] Update configure-hash-rings.md fix a switch of value for
 cluster-label-verification-disabled

> 5. Enable cluster label verification on all clusters instances by removing the configuration option `-memberlist.cluster-label-verification-disabled=true`.

Need to be false if we want to enable cluster-label-verification-disabled :

> 5. Enable cluster label verification on all clusters instances by removing the configuration option `-memberlist.cluster-label-verification-disabled=false`.
---
 docs/sources/mimir/configure/configure-hash-rings.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/sources/mimir/configure/configure-hash-rings.md b/docs/sources/mimir/configure/configure-hash-rings.md
index 765b598d4dc..953c75f11e2 100644
--- a/docs/sources/mimir/configure/configure-hash-rings.md
+++ b/docs/sources/mimir/configure/configure-hash-rings.md
@@ -108,7 +108,7 @@ Any traffic that does not match that prefix is discarded, to ensure that only th
    This label must be the same on all instances that are part of the same cluster.
    For example, if you run a Grafana Mimir cluster in a dedicated namespace, then set the cluster label to the name of the namespace.
 4. **Wait** until the configuration change has been rolled out to all Grafana Mimir instances.
-5. Enable cluster label verification on all clusters instances by removing the configuration option `-memberlist.cluster-label-verification-disabled=true`.
+5. Enable cluster label verification on all clusters instances by removing the configuration option `-memberlist.cluster-label-verification-disabled=false`.
 6. **Wait** until the configuration change has been rolled out to all Grafana Mimir instances.
 
 ### Fine tuning memberlist changes propagation latency