diff --git a/calico-enterprise/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx b/calico-enterprise/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx
index 4380f070bb..aad9f7d4a9 100644
--- a/calico-enterprise/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx
+++ b/calico-enterprise/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx
@@ -38,6 +38,18 @@ the upgrade.
 
 If your cluster has Windows nodes and uses custom TLS certificates for log storage then, prior to upgrade, prepare and apply new certificates for [log storage](../../../../operations/comms/index.mdx) that include the required service DNS names.
 
+### Compliance
+
+The Compliance feature is removed in this release. Delete the Compliance resource before you upgrade, so that Kubernetes garbage collects the compliance deployments, service accounts, and RBAC that it owns.
+
+```bash
+kubectl delete compliance tigera-secure
+```
+
+If you manage $[prodname] resources with GitOps tooling, remove the Compliance resource from your source manifests as well. Otherwise the tooling recreates it after you upgrade.
+
+If you receive an error indicating the resource or resource type does not exist, Compliance was not installed in your cluster. You can safely ignore the error and proceed.
+
 ### Upgrade OwnerReferences
 
 If you do not use OwnerReferences on resources in the projectcalico.org/v3 API group, you can skip this section.
diff --git a/calico-enterprise/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/operator.mdx b/calico-enterprise/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/operator.mdx
index 788acedd08..936609fa08 100644
--- a/calico-enterprise/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/operator.mdx
+++ b/calico-enterprise/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/operator.mdx
@@ -45,6 +45,18 @@ have their reclaim policy set to [retain data](https://kubernetes.io/docs/tasks/
 Retaining data is only recommended for users that use a valid Elastic license. Trial licenses can get invalidated during
 the upgrade.
 
+### Compliance
+
+The Compliance feature is removed in this release. Delete the Compliance resource before you upgrade, so that Kubernetes garbage collects the compliance deployments, service accounts, and RBAC that it owns.
+
+```bash
+kubectl delete compliance tigera-secure
+```
+
+If you manage $[prodname] resources with GitOps tooling, remove the Compliance resource from your source manifests as well. Otherwise the tooling recreates it after you upgrade.
+
+If you receive an error indicating the resource or resource type does not exist, Compliance was not installed in your cluster. You can safely ignore the error and proceed.
+
 ### Upgrade OwnerReferences
 
 If you do not use OwnerReferences on resources in the projectcalico.org/v3 API group, you can skip this section.
diff --git a/calico-enterprise/getting-started/upgrading/upgrading-enterprise/openshift-upgrade.mdx b/calico-enterprise/getting-started/upgrading/upgrading-enterprise/openshift-upgrade.mdx
index cb08b2d7a2..d2d99d3f36 100644
--- a/calico-enterprise/getting-started/upgrading/upgrading-enterprise/openshift-upgrade.mdx
+++ b/calico-enterprise/getting-started/upgrading/upgrading-enterprise/openshift-upgrade.mdx
@@ -48,6 +48,18 @@ have their reclaim policy set to [retain data](https://kubernetes.io/docs/tasks/
 Data retention is recommended only for users that have a valid Elasticsearch license. (Trial licenses can be invalidated
 during upgrade).
 
+### Compliance
+
+The Compliance feature is removed in this release. Delete the Compliance resource before you upgrade, so that Kubernetes garbage collects the compliance deployments, service accounts, and RBAC that it owns.
+
+```bash
+oc delete compliance tigera-secure
+```
+
+If you manage $[prodname] resources with GitOps tooling, remove the Compliance resource from your source manifests as well. Otherwise the tooling recreates it after you upgrade.
+
+If you receive an error indicating the resource or resource type does not exist, Compliance was not installed in your cluster. You can safely ignore the error and proceed.
+
 ### Upgrade OwnerReferences
 
 If you do not use OwnerReferences on resources in the projectcalico.org/v3 API group, you can skip this section.