diff --git a/docs/integrations/platforms/kubernetes/infisical-secret-crd.mdx b/docs/integrations/platforms/kubernetes/infisical-secret-crd.mdx
index f263b518a..9e01f36d9 100644
--- a/docs/integrations/platforms/kubernetes/infisical-secret-crd.mdx
+++ b/docs/integrations/platforms/kubernetes/infisical-secret-crd.mdx
@@ -672,6 +672,10 @@ When you set `includeAllSecrets` as `false` the Kubernetes secrets outputs will
 {"NEW_KEY":"LyBoZWxsbw=="}
 ```
 
+Available Template Functions
+
+- `base64DecodeBytes`: Converts a base64-encoded string into a byte array. This is commonly used for storing binary data in Infisical as base64 and syncing it with the operator. However, Kubernetes also performs base64 encoding, leading to double base64 conversion. To avoid this, you can decode the base64 string just before saving it to the operator.
+
 </Accordion>
 <Accordion title="managedSecretReference.creationPolicy">
 Creation polices allow you to control whether or not owner references should be added to the managed Kubernetes secret that is generated by the Infisical operator. 
@@ -960,4 +964,5 @@ metadata:
 type: Opaque
 ```
 
-</Accordion>
\ No newline at end of file
+</Accordion>
+