Skip to content

Infisical is the open-source platform for securing secrets, certificates, access, and AI Agents.

Update infisical-static-secret-crd.mdx

varonix0f240c699000
diff --git a/docs/integrations/platforms/kubernetes/infisical-static-secret-crd.mdx b/docs/integrations/platforms/kubernetes/infisical-static-secret-crd.mdx
index bf880a328f..73a278f7d6 100644
--- a/docs/integrations/platforms/kubernetes/infisical-static-secret-crd.mdx
+++ b/docs/integrations/platforms/kubernetes/infisical-static-secret-crd.mdx
@@ -1075,19 +1075,25 @@ The `InfisicalStaticSecret` spec is different from the `InfisicalSecret` spec:
</Note>
</Step>
<Step>
- When the `SYNCED` column shows `True` for the `InfisicalStaticSecret`, delete the `InfisicalSecret`:
+ Check that the `SYNCED` column shows `True` for the `InfisicalStaticSecret`:
```bash
kubectl get infisicalstaticsecret <static-secret-name> -n <namespace>
- kubectl delete infisicalsecret <infisical-secret-name> -n <namespace>
```
- The Secrets and ConfigMaps stay in place, and the `InfisicalStaticSecret` manages them from now on.
-
<Warning>
- Don't delete the `InfisicalSecret` before `SYNCED` shows `True`. If you do, Kubernetes can delete the Secrets and ConfigMaps, and the operator creates them again only at the next `refreshInterval`.
+ Don't go to the next step before `SYNCED` shows `True`. If you delete the `InfisicalSecret` too early, Kubernetes can delete the Secrets and ConfigMaps, and the operator creates them again only at the next `refreshInterval`.
</Warning>
</Step>
+ <Step>
+ Delete the `InfisicalSecret`:
+
+ ```bash
+ kubectl delete infisicalsecret <infisical-secret-name> -n <namespace>
+ ```
+
+ The Secrets and ConfigMaps stay in place, and the `InfisicalStaticSecret` manages them from now on.
+ </Step>
</Steps>
### How the migration works