feat: add auto redeploy for daemonset and statefulset

docs/integrations/platforms/kubernetes/infisical-secret-crd.mdx

@@ -547,12 +547,14 @@ The `managedSecretReference` field is deprecated and will be removed in a future
 Replace it with `managedKubeSecretReferences`, which now accepts an array of references to support multiple managed secrets in a single InfisicalSecret CRD.
 
 Example:
+
 ```yaml
-  managedKubeSecretReferences:
-    - secretName: managed-secret
-      secretNamespace: default
-      creationPolicy: "Orphan"
+managedKubeSecretReferences:
+  - secretName: managed-secret
+    secretNamespace: default
+    creationPolicy: "Orphan"
 ```
+
 </Note>
 
 <Accordion title="managedKubeSecretReferences">
@@ -666,13 +668,13 @@ The example below assumes that the `BINARY_KEY_BASE64` secret is stored as a bas
 The resulting managed secret will contain the decoded value of `BINARY_KEY_BASE64`.
 
 ```yaml
-  managedKubeSecretReferences:
-  secretName: managed-secret
-  secretNamespace: default
-  template:
-    includeAllSecrets: true
-    data:
-      BINARY_KEY: "{{ decodeBase64ToBytes .BINARY_KEY_BASE64.Value }}"
+managedKubeSecretReferences:
+secretName: managed-secret
+secretNamespace: default
+template:
+  includeAllSecrets: true
+  data:
+    BINARY_KEY: "{{ decodeBase64ToBytes .BINARY_KEY_BASE64.Value }}"
 ```
 
 </Accordion>
@@ -866,7 +868,7 @@ To address this, we added functionality to automatically redeploy your deploymen
 
 #### Enabling auto redeploy
 
-To enable auto redeployment you simply have to add the following annotation to the deployment that consumes a managed secret
+To enable auto redeployment you simply have to add the following annotation to the deployment, statefulset, or daemonset that consumes a managed secret.
 
 ```yaml
 secrets.infisical.com/auto-reload: "true"
@@ -948,4 +950,4 @@ metadata:
 type: Opaque
 ```
 
-</Accordion>
+</Accordion>