Skip to content
9 changes: 9 additions & 0 deletions content/en/containers/kubernetes/csi_driver.md
Original file line number Diff line number Diff line change
Expand Up @@ -170,6 +170,15 @@

{{% /collapse-content %}}

#### Upgrade and migration notes

<div class="alert alert-warning">
<strong>Upgrading the Datadog Operator to v1.28.0+ from v1.26.0 or v1.27.0</strong>
<p>If you previously ran <code>v1.26.0</code> or <code>v1.27.0</code>, upgrading to Datadog Operator <code>v1.28.0</code> or later can leave the built-in Kubernetes <code>CSIDriver</code> object (not the <code>DatadogCSIDriver</code> custom resource) in a state that the Operator cannot reconcile. Remediate this issue by deleting the object:</p>

Check notice on line 177 in content/en/containers/kubernetes/csi_driver.md

View workflow job for this annotation

GitHub Actions / vale

Datadog.sentencelength

Suggestion: Try to keep your sentence length to 25 words or fewer.
<pre><code>kubectl delete csidriver k8s.csi.datadoghq.com</code></pre>
<p>The Operator recreates it automatically. Already-mounted volumes and running driver pods are unaffected.</p>
</div>

Comment thread
mrdoggopat marked this conversation as resolved.
Outdated
<div class="alert alert-warning">
<strong>Migrating from Helm-based CSI Driver installation</strong>
<p>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:</p>
Expand Down
Loading