From 462bb6eb6956264afadf6d96692b3b75d999e86a Mon Sep 17 00:00:00 2001
From: Will <28876888+willtsai@users.noreply.github.com>
Date: Tue, 16 Sep 2025 09:42:00 -0700
Subject: [PATCH] Upgrading docs - remove warning about CRDs (#1523)

Signed-off-by: Will Tsai <28876888+willtsai@users.noreply.github.com>
(cherry picked from commit 2e057cc8dd76a93a2e146a989be76ce8b3a51ff8)
---
 .../operations/kubernetes/kubernetes-upgrade/index.md       | 6 ------
 1 file changed, 6 deletions(-)

diff --git a/docs/content/guides/operations/kubernetes/kubernetes-upgrade/index.md b/docs/content/guides/operations/kubernetes/kubernetes-upgrade/index.md
index e171d9697..f68837244 100644
--- a/docs/content/guides/operations/kubernetes/kubernetes-upgrade/index.md
+++ b/docs/content/guides/operations/kubernetes/kubernetes-upgrade/index.md
@@ -75,12 +75,6 @@ rad env list
 
 ## Important considerations
 
-### CRD updates
-
-> **Note:** Due to a [Helm limitation](https://helm.sh/docs/chart_best_practices/custom_resource_definitions/), Custom Resource Definitions (CRDs) are only installed during the initial Radius installation and are not automatically updated during upgrades.
->
-> If a Radius upgrade includes CRD changes (typically in major version upgrades), you may need to manually update the CRDs. Check the release notes for specific instructions when CRD updates are required.
-
 ### Breaking changes
 
 While Radius supports in-place upgrades, breaking changes may still occur between major versions. Always review the [release notes](https://github.com/radius-project/radius/releases) before upgrading to understand any breaking changes or migration steps required.