From 94ff82361dd621f6974850f1cbe635694d0f8b66 Mon Sep 17 00:00:00 2001 From: mrmcpat Date: Wed, 8 Jul 2026 09:32:09 -0400 Subject: [PATCH 01/10] Add warning to CSI Driver docs on upgrading to Datadog Operator 1.28.0 --- content/en/containers/kubernetes/csi_driver.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/content/en/containers/kubernetes/csi_driver.md b/content/en/containers/kubernetes/csi_driver.md index ee2c7e0247f..cc2328b1da0 100644 --- a/content/en/containers/kubernetes/csi_driver.md +++ b/content/en/containers/kubernetes/csi_driver.md @@ -170,6 +170,13 @@ If you need configuration options not exposed through the `DatadogAgent` spec (f {{% /collapse-content %}} +
+Upgrading the Datadog Operator to v1.28.0 or later +

In some cases, upgrading to Datadog Operator v1.28.0 or later can leave the existing k8s.csi.datadoghq.com CSIDriver object in a state that the Operator cannot reconcile. If the CSI Driver does not become ready after upgrading, recreate the object once:

+
kubectl delete csidriver k8s.csi.datadoghq.com
+

The Operator recreates it automatically. Already-mounted volumes and running driver Pods are unaffected.

+
+
Migrating from Helm-based CSI Driver installation

If you previously installed the CSI Driver with the standalone Helm chart, Datadog recommends migrating to Operator-managed installation. Choose one of the following approaches:

From 8187552bf4555893cf03801d55a3f6871466b8b6 Mon Sep 17 00:00:00 2001 From: mrmcpat <109171317+mrdoggopat@users.noreply.github.com> Date: Wed, 8 Jul 2026 09:45:44 -0400 Subject: [PATCH 02/10] Update content/en/containers/kubernetes/csi_driver.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Timothée Bavelier <97530782+tbavelier@users.noreply.github.com> --- content/en/containers/kubernetes/csi_driver.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/containers/kubernetes/csi_driver.md b/content/en/containers/kubernetes/csi_driver.md index cc2328b1da0..f6cac3c406c 100644 --- a/content/en/containers/kubernetes/csi_driver.md +++ b/content/en/containers/kubernetes/csi_driver.md @@ -171,8 +171,8 @@ If you need configuration options not exposed through the `DatadogAgent` spec (f {{% /collapse-content %}}
-Upgrading the Datadog Operator to v1.28.0 or later -

In some cases, upgrading to Datadog Operator v1.28.0 or later can leave the existing k8s.csi.datadoghq.com CSIDriver object in a state that the Operator cannot reconcile. If the CSI Driver does not become ready after upgrading, recreate the object once:

+Upgrading the Datadog Operator to v1.28.0+ from v1.26.0 and v1.27.0 +

If previously running v1.26.0 or v1.27.0, upgrading to Datadog Operator v1.28.0 or later can leave the existing k8s.csi.datadoghq.com CSIDriver object in a state that the Operator cannot reconcile. Remediate by recreating the object once:

kubectl delete csidriver k8s.csi.datadoghq.com

The Operator recreates it automatically. Already-mounted volumes and running driver Pods are unaffected.

From 528d2cc6b5a242349609571d46fc3af3e4066cb8 Mon Sep 17 00:00:00 2001 From: mrmcpat <109171317+mrdoggopat@users.noreply.github.com> Date: Wed, 8 Jul 2026 09:50:40 -0400 Subject: [PATCH 03/10] Update content/en/containers/kubernetes/csi_driver.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Timothée Bavelier <97530782+tbavelier@users.noreply.github.com> --- content/en/containers/kubernetes/csi_driver.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/containers/kubernetes/csi_driver.md b/content/en/containers/kubernetes/csi_driver.md index f6cac3c406c..da48cac2727 100644 --- a/content/en/containers/kubernetes/csi_driver.md +++ b/content/en/containers/kubernetes/csi_driver.md @@ -172,7 +172,7 @@ If you need configuration options not exposed through the `DatadogAgent` spec (f
Upgrading the Datadog Operator to v1.28.0+ from v1.26.0 and v1.27.0 -

If previously running v1.26.0 or v1.27.0, upgrading to Datadog Operator v1.28.0 or later can leave the existing k8s.csi.datadoghq.com CSIDriver object in a state that the Operator cannot reconcile. Remediate by recreating the object once:

+

If previously running v1.26.0 or v1.27.0, upgrading to Datadog Operator v1.28.0 or later can leave the existing k8s.csi.datadoghq.com CSIDriver object in a state that the Operator cannot reconcile. Remediate by deleting the object once:

kubectl delete csidriver k8s.csi.datadoghq.com

The Operator recreates it automatically. Already-mounted volumes and running driver Pods are unaffected.

From c628c3f8e37b9bb57cc87f3fb1ccf6866c4f8687 Mon Sep 17 00:00:00 2001 From: mrmcpat <109171317+mrdoggopat@users.noreply.github.com> Date: Wed, 8 Jul 2026 10:21:31 -0400 Subject: [PATCH 04/10] Update content/en/containers/kubernetes/csi_driver.md Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> --- content/en/containers/kubernetes/csi_driver.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/containers/kubernetes/csi_driver.md b/content/en/containers/kubernetes/csi_driver.md index da48cac2727..b2cd21747df 100644 --- a/content/en/containers/kubernetes/csi_driver.md +++ b/content/en/containers/kubernetes/csi_driver.md @@ -174,7 +174,7 @@ If you need configuration options not exposed through the `DatadogAgent` spec (f Upgrading the Datadog Operator to v1.28.0+ from v1.26.0 and v1.27.0

If previously running v1.26.0 or v1.27.0, upgrading to Datadog Operator v1.28.0 or later can leave the existing k8s.csi.datadoghq.com CSIDriver object in a state that the Operator cannot reconcile. Remediate by deleting the object once:

kubectl delete csidriver k8s.csi.datadoghq.com
-

The Operator recreates it automatically. Already-mounted volumes and running driver Pods are unaffected.

+

The Operator recreates it automatically. Already-mounted volumes and running driver pods are unaffected.

From 71dca34d82493ce7f60183f4e5e0513e90c959c8 Mon Sep 17 00:00:00 2001 From: mrmcpat <109171317+mrdoggopat@users.noreply.github.com> Date: Wed, 8 Jul 2026 10:21:46 -0400 Subject: [PATCH 05/10] Update content/en/containers/kubernetes/csi_driver.md Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> --- content/en/containers/kubernetes/csi_driver.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/containers/kubernetes/csi_driver.md b/content/en/containers/kubernetes/csi_driver.md index b2cd21747df..a17bb8b7b8a 100644 --- a/content/en/containers/kubernetes/csi_driver.md +++ b/content/en/containers/kubernetes/csi_driver.md @@ -171,7 +171,7 @@ If you need configuration options not exposed through the `DatadogAgent` spec (f {{% /collapse-content %}}
-Upgrading the Datadog Operator to v1.28.0+ from v1.26.0 and v1.27.0 +Upgrading the Datadog Operator to v1.28.0+ from v1.26.0 or v1.27.0

If previously running v1.26.0 or v1.27.0, upgrading to Datadog Operator v1.28.0 or later can leave the existing k8s.csi.datadoghq.com CSIDriver object in a state that the Operator cannot reconcile. Remediate by deleting the object once:

kubectl delete csidriver k8s.csi.datadoghq.com

The Operator recreates it automatically. Already-mounted volumes and running driver pods are unaffected.

From 04632d6d06e8eb95e9e6db1f56c1af431c2f595e Mon Sep 17 00:00:00 2001 From: mrmcpat <109171317+mrdoggopat@users.noreply.github.com> Date: Wed, 8 Jul 2026 10:23:56 -0400 Subject: [PATCH 06/10] Update csi_driver.md --- content/en/containers/kubernetes/csi_driver.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/containers/kubernetes/csi_driver.md b/content/en/containers/kubernetes/csi_driver.md index a17bb8b7b8a..9c5de238042 100644 --- a/content/en/containers/kubernetes/csi_driver.md +++ b/content/en/containers/kubernetes/csi_driver.md @@ -172,7 +172,7 @@ If you need configuration options not exposed through the `DatadogAgent` spec (f
Upgrading the Datadog Operator to v1.28.0+ from v1.26.0 or v1.27.0 -

If previously running v1.26.0 or v1.27.0, upgrading to Datadog Operator v1.28.0 or later can leave the existing k8s.csi.datadoghq.com CSIDriver object in a state that the Operator cannot reconcile. Remediate by deleting the object once:

+

If you previously ran v1.26.0 or v1.27.0, upgrading to Datadog Operator v1.28.0 or later can leave the existing k8s.csi.datadoghq.com CSIDriver object in a state that the Operator cannot reconcile. Remediate by deleting the object once:

kubectl delete csidriver k8s.csi.datadoghq.com

The Operator recreates it automatically. Already-mounted volumes and running driver pods are unaffected.

From ea46ac86a41333755e4ae359b15e51ad6a8b98c5 Mon Sep 17 00:00:00 2001 From: mrmcpat <109171317+mrdoggopat@users.noreply.github.com> Date: Wed, 8 Jul 2026 12:56:59 -0400 Subject: [PATCH 07/10] Update content/en/containers/kubernetes/csi_driver.md Co-authored-by: Bryce Eadie --- content/en/containers/kubernetes/csi_driver.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/containers/kubernetes/csi_driver.md b/content/en/containers/kubernetes/csi_driver.md index 9c5de238042..369e6c7a908 100644 --- a/content/en/containers/kubernetes/csi_driver.md +++ b/content/en/containers/kubernetes/csi_driver.md @@ -172,7 +172,7 @@ If you need configuration options not exposed through the `DatadogAgent` spec (f
Upgrading the Datadog Operator to v1.28.0+ from v1.26.0 or v1.27.0 -

If you previously ran v1.26.0 or v1.27.0, upgrading to Datadog Operator v1.28.0 or later can leave the existing k8s.csi.datadoghq.com CSIDriver object in a state that the Operator cannot reconcile. Remediate by deleting the object once:

+

If you previously ran v1.26.0 or v1.27.0, upgrading to Datadog Operator v1.28.0 or later can leave the built-in Kubernetes CSIDriver object (not the DatadogCSIDriver custom resource) in a state that the Operator cannot reconcile. Remediate this issue by deleting the object:

kubectl delete csidriver k8s.csi.datadoghq.com

The Operator recreates it automatically. Already-mounted volumes and running driver pods are unaffected.

From bf12c604bee0f6a0804e31da1f5c029c46dba048 Mon Sep 17 00:00:00 2001 From: mrmcpat Date: Wed, 8 Jul 2026 13:10:27 -0400 Subject: [PATCH 08/10] add subheading before the warning divs --- content/en/containers/kubernetes/csi_driver.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/en/containers/kubernetes/csi_driver.md b/content/en/containers/kubernetes/csi_driver.md index 369e6c7a908..d169b7f784a 100644 --- a/content/en/containers/kubernetes/csi_driver.md +++ b/content/en/containers/kubernetes/csi_driver.md @@ -170,6 +170,8 @@ If you need configuration options not exposed through the `DatadogAgent` spec (f {{% /collapse-content %}} +#### Upgrade and migration notes +
Upgrading the Datadog Operator to v1.28.0+ from v1.26.0 or v1.27.0

If you previously ran v1.26.0 or v1.27.0, upgrading to Datadog Operator v1.28.0 or later can leave the built-in Kubernetes CSIDriver object (not the DatadogCSIDriver custom resource) in a state that the Operator cannot reconcile. Remediate this issue by deleting the object:

From 9477b7750d9f1aa6e7e917b84ee4feb5ea9baaf4 Mon Sep 17 00:00:00 2001 From: mrmcpat <109171317+mrdoggopat@users.noreply.github.com> Date: Fri, 10 Jul 2026 13:45:17 -0400 Subject: [PATCH 09/10] Update content/en/containers/kubernetes/csi_driver.md Co-authored-by: Bryce Eadie --- content/en/containers/kubernetes/csi_driver.md | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/content/en/containers/kubernetes/csi_driver.md b/content/en/containers/kubernetes/csi_driver.md index d169b7f784a..4313dce1da0 100644 --- a/content/en/containers/kubernetes/csi_driver.md +++ b/content/en/containers/kubernetes/csi_driver.md @@ -170,15 +170,20 @@ If you need configuration options not exposed through the `DatadogAgent` spec (f {{% /collapse-content %}} -#### Upgrade and migration notes +#### Upgrading to Datadog Operator v1.28.0+
-Upgrading the Datadog Operator to v1.28.0+ from v1.26.0 or v1.27.0 -

If you previously ran v1.26.0 or v1.27.0, upgrading to Datadog Operator v1.28.0 or later can leave the built-in Kubernetes CSIDriver object (not the DatadogCSIDriver custom resource) in a state that the Operator cannot reconcile. Remediate this issue by deleting the object:

+

If you previously ran v1.26.0 or v1.27.0, upgrading to Datadog Operator v1.28.0 or later can leave the built-in Kubernetes CSIDriver object (not the DatadogCSIDriver custom resource) in a state that the Operator cannot reconcile. To resolve this issue, delete the object:

kubectl delete csidriver k8s.csi.datadoghq.com

The Operator recreates it automatically. Already-mounted volumes and running driver pods are unaffected.

+#### Migrating from a Helm-based installation + +If you previously installed the CSI Driver with the standalone Helm chart, Datadog recommends migrating to Operator-managed installation. Choose one of the following approaches: + +- **Let the Operator manage the CSI Driver**: Uninstall the Helm chart (`helm uninstall datadog-csi-driver`) and keep the default values for `csi.enabled` and `csi.autoManage`. The Operator automatically creates a new `DatadogCSIDriver` resource and deploys the driver. +- **Keep managing the CSI Driver with Helm**: No action is required. The Operator detects the existing `k8s.csi.datadoghq.com` CSIDriver and defers to it, regardless of the `csi.autoManage` value. The Operator does not interfere with your existing Helm-managed driver. To make this intent explicit, set `csi.autoManage: false`.
Migrating from Helm-based CSI Driver installation

If you previously installed the CSI Driver with the standalone Helm chart, Datadog recommends migrating to Operator-managed installation. Choose one of the following approaches:

From 0b79a92c0fc29d221272890238f33ff15d46ee8b Mon Sep 17 00:00:00 2001 From: Bryce Eadie Date: Fri, 10 Jul 2026 10:52:24 -0700 Subject: [PATCH 10/10] Remove redundant warning --- content/en/containers/kubernetes/csi_driver.md | 8 -------- 1 file changed, 8 deletions(-) diff --git a/content/en/containers/kubernetes/csi_driver.md b/content/en/containers/kubernetes/csi_driver.md index 4313dce1da0..739afbf6df3 100644 --- a/content/en/containers/kubernetes/csi_driver.md +++ b/content/en/containers/kubernetes/csi_driver.md @@ -184,14 +184,6 @@ If you previously installed the CSI Driver with the standalone Helm chart, Datad - **Let the Operator manage the CSI Driver**: Uninstall the Helm chart (`helm uninstall datadog-csi-driver`) and keep the default values for `csi.enabled` and `csi.autoManage`. The Operator automatically creates a new `DatadogCSIDriver` resource and deploys the driver. - **Keep managing the CSI Driver with Helm**: No action is required. The Operator detects the existing `k8s.csi.datadoghq.com` CSIDriver and defers to it, regardless of the `csi.autoManage` value. The Operator does not interfere with your existing Helm-managed driver. To make this intent explicit, set `csi.autoManage: false`. -
-Migrating from Helm-based CSI Driver installation -

If you previously installed the CSI Driver with the standalone Helm chart, Datadog recommends migrating to Operator-managed installation. Choose one of the following approaches:

-
    -
  • Let the Operator manage the CSI Driver: Uninstall the Helm chart (helm uninstall datadog-csi-driver) and keep the default values for csi.enabled and csi.autoManage. The Operator automatically creates a new DatadogCSIDriver resource and deploys the driver.
    • -
  • Keep managing the CSI Driver with Helm: No action is required. The Operator detects the existing k8s.csi.datadoghq.com CSIDriver and defers to it, regardless of the csi.autoManage value. The Operator does not interfere with your existing Helm-managed driver. To make this intent explicit, set csi.autoManage: false.
    • -
-
{{% collapse-content title="Legacy Helm-based installation (Operator < v1.26.0)" level="h4" id="legacy-helm-based-installation" %}}