From 05339dafe5a70e409caed40a5bde2bca6b4c486b Mon Sep 17 00:00:00 2001
From: Max Gautier <mg@max.gautier.name>
Date: Thu, 13 Jun 2024 11:03:11 +0200
Subject: [PATCH] Remove misleading documentation about config generation

ConfigMap are not garbage collected, see #3146
---
 examples/configGeneration.md | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/examples/configGeneration.md b/examples/configGeneration.md
index 8314b8955d..ca912f38cb 100644
--- a/examples/configGeneration.md
+++ b/examples/configGeneration.md
@@ -113,9 +113,7 @@ configuration is to
     the appropriate `configMapKeyRef` field.
 
 This latter change initiates rolling update to the pods
-in the deployment. The older ConfigMap, when no longer
-referenced by any other resource, is eventually [garbage
-collected](/../../issues/242).
+in the deployment.
 
 ### How this works with kustomize